The ability to register both A and PTR type records lets a DHCP server act as a proxy for clients using Microsoft Windows 95 and Windows NT 4.0 for the purpose of DNS registration.
DHCP servers can differentiate between Windows 2000 and other clients.
For example, a client may acquire its IP address from a DHCP server, but the DNS records would not reflect the IP address acquired nor provide a mapping from the new IP address to the computer name (FQDN).
In Windows 2000, DHCP servers and clients can register with DNS to provide this update service if the DNS server supports DNS with dynamic updates.
These can be added to DNS and will always be available. But, I need a pool for a set of virtual hosts that are being configured. config files, but my DHCP/DNS provides the IP addresses as the vhosts are launched or retired.
When a new client gets an IP address, DHCP doesn't update DNS with the record. The DHCP and DNS are on the same box (which is also the primary DC).
Click Here to receive this Complete Guide absolutely free.
So I've searched and searched....from one side of the net to the other and I can't seem to find a solution to my problem.
While DHCP provides a powerful mechanism for automatically configuring client IP addresses, until recently DHCP did not notify the DNS service to update the DNS records on the client; specifically, updating the client name to an IP address, and IP address to name mappings maintained by a DNS server.
Without a way for DHCP to interact with DNS, the information maintained by DNS for a DHCP client may be incorrect.
I have checked the event viewer logs for the DHCP and DNS server but nothing is present?