[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1305
  • Last Modified:

DNS Resolver Not Appending Connection Specific DNS Suffix

I have a vista laptop which I use and many different sites, some which have proxy servers and some which don't.
At each site I am confuring a automatic proxy configuration file. at site domain.local the file is configured to be http://wpad.domain.local:80/wpad.dat
Browsers attempt to resolve wpad, which should append the connection specific DNS suffix, in this case domain.local, and then look for the wpad.dat on that web server.
To test the domain name resolution I type in "ping wpad" and it does not resolve.  This is my problem.
If I type in "ping wpad.domain.local" it resolves fine.  if I change the primary suffix for the computer to domain.local and reboot, then it will work with just "ping wpad", however I don't want to reconfigure the primary domain suffix for each site I visit. (It would be easier to change the proxy setting).

What I don't understand is why the connection specific dns suffixes are not being used.  I can clearly see the suffix when I do an ipconfig/all on both my wireless and/or local area connection as applicable.

The computer is not part of a domain and no group policies are in play here.
1 Solution
bevhostAuthor Commented:
Just discovered that it works if I disable the VMWare Server adapters. (VMnet1 & VMnet8)
Not sure why that has anything to do with it.

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now