Dhcp server is not updating dns records
In this article, I will discuss ways in which you can achieve this goal.
There are two ways you can migrate your DNS services to Windows Server 2008 — although one is definitely better than the other.
Uptown DC will be the primary DNS server for and for a 192.168.0.x reverse-lookup zone, and it will be the secondary DNS server for a 10.0.0.x reverse-lookup zone.
ISA Server firewall/VPN servers and clients use DNS host name resolution to resolve both internal and external network names.
In past Inside Out columns, I've shown you how to use simple batch files to set up just-installed systems as domain controllers (DCs) and to create disaster-recovery tools.
I've also shown you how to use Netsh to configure and fine-tune your IP stack—the first step toward making a Windows Server 2003 or Windows 2000 server ready to ascend to DC status.
However, that DNS server address does not resolve names on the corporate network because that DNS server is intended to resolve names on the network the VPN client computer is attached to before connecting to the ISA firewall/VPN server, or to resolve only Internet host names.
The VPN client that cannot resolve internal network names may have been assigned an incorrect DNS server address.