RRAS passing DNS resolution requests.

  • Thread starter Thread starter Haggis
  • Start date Start date
H

Haggis

I have posted this in addition to an exact problem in
this discussion group titled: 'Unknown case of VPN
routing Issue' Sep 18th

I have a weird problem. My VPN clients can't resolve DNS
names through RRAS. Central LAN has no problems. IP
resolution is not a prob for VPN clients. (To patch the
problem i had to run hosts files). When VPN clients ping
a DNS name (main server) we get a return for an incorrect
IP (totally wrong). So it seems they are not resolving
dns names from our dns server but from a dns server on
the internet. I have tried changing the 'Default gateway
on remote network' setting on the VPN properties, no joy.
Ipconfig reveals that the have got the correct DNS
servers configured from the DHCP relay agent.

Main server is now upgraded to 2003 and still the problem
persists.
 
They may have the correct DNS server IP address, but what DNS suffix
do they use?

In the client's connection properties, go to the advanced TCP/IP
settings and then the DNS tab. Make sure that the DNS suffix(es) of the Main
Office DNS domains are listed in the "Append these DNS suffixes" box.
 
Yeah, makes no difference
-----Original Message-----
They may have the correct DNS server IP address, but what DNS suffix
do they use?

In the client's connection properties, go to the advanced TCP/IP
settings and then the DNS tab. Make sure that the DNS suffix(es) of the Main
Office DNS domains are listed in the "Append these DNS suffixes" box.




.
Click to expand...
 
Yes, it certainly sounds like a DNS problem linked to the Verisign
changes. See the windows.server.dns newsgroup for more details.
 
How did you fix the 64.94.110.11 response when ever a vpn
client tried to resolve an internal host name
 
Back
Top