SearchNetworking.com

When users have been connecting to our VPN servers they are unable to resolve host name information.

We currently run Microsoft RRAS for remote users using high-speed connections. When our client's connect they receive network config info from our DHCP server, dns, ip, wins.

Recently, when users have been connecting to our VPN servers they are unable to resolve host name information. When we do a ping or traceroute to an internal hostname, the request times out and the internal hostname that it tries to resolve is 64.94.110.11. When I do an NSLOOKUP, the default DNS server is the ISP's and not our internal DNS servers. All our office users internally are having no problems resolving hostnames and such. I know that the address I mentioned is VeriSign sitefinder address that they just implemented. The problem started around the time VeriSign added the wildcard to the root servers. Have you heard of anything like this? I would appreciate your input.

    Requires Free Membership to View

All Rights Reserved, Copyright 2000 - 2013 , TechTarget | Read our Privacy Statement