Lately all of my VPN users have been having a problem.
When they log on to the companys network remotely via VPN,
their workstations are not able to resolve DNS names. If I
prompt them to use IP addresses of servers then they are
able to reach network resources. I have verified that they
all
have the right IP for the internal DNS server from DHCP.
IS it possible that DNS is responding to a different IP
addy after it resolves the name? Our VPN servers IP was
accidentally changed (192.168.1.51) for a few days, but
has since been changed back to the old one (192.168.1.7)
Could DNS have cached this change of IP and not show it in
an NSLOOKUP ls command?
Any help is greatly appreciated!

Answered my own question. It looks as though the INternal
interface for DHCP relay was missing. I added it back and
all was fine. So, DHCP relay MUST be on for DNS name
resolution to work!

In news:0a6f01c352ba$053219b0$(E-Mail Removed),
barteem <(E-Mail Removed)> posted his concerns then I replied down below:
> Answered my own question. It looks as though the INternal
> interface for DHCP relay was missing. I added it back and
> all was fine. So, DHCP relay MUST be on for DNS name
> resolution to work!

Strange, DHCP relay agent is not required for DNS. Maybe because the relay
agent was misconfigured, it wasn't passing the proper DHCP options?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
--
=================================