I am having an issue with resolving a DNS hostname while using Cisco AnyConnect connecting to an ASA. The end user profile is setup for split tunneling to send only traffic to our servers through the VPN.
Their Windows PC is on a separate domain from our server. The user can access the server via FQDN but the application they will be using only points to the server hostname and is unable to change the configuration. What is strange is we have had consultants from different companies who have not had any issue resolving servers by hostname only and are using identical profile settings.
My first thought would be to configure the profile to resolve all DNS settings. That would get the issue fix but could cause more problems on the user's side. Another thought is to have them change their HOSTS file to statically map the server to our internal IP. Unsure if there was a way to push a single DNS entry without user intervention.
I appreciate any feedback or insight!
No comments:
Post a Comment