For updated detailed IT pro information about DHCP and DNS, see the Windows Server 2008 documentation on the Microsoft Tech Net Web site.
It's somewhere on one of these servers, over here. Try searching for similar questions Browse our recent questions Browse our popular tags If you feel something is missing that should be here, contact us.
When a DHCP server registers and updates DNS pointer (PTR) and address (A) resource records on behalf of its DHCP-enabled clients, it uses the information contained within an additional DHCP option: the Client FQDN option (option 81), which permits a client to provide its FQDN and any instructions to the DHCP server that is used to process DNS dynamic updates on its behalf.
The following reasons or events can trigger a dynamic update: When one of these events triggers a dynamic update, the DNS Client service (not the DHCP Client service) sends updates.
Archived from groups: microsoft.public.win2000(More info? )Server 2000 SP4 Domain Controller (bigorange.local)Active Directory integrated DNS (forward and reverse)Test Environment, not connected to the Internet Server 2003, NT 4.0 and XP Pro Clients (1 each)dcpromo created my dns and I deleted the root zone.
I created my reverse zone and added a forward zone bigorange.local - when I add computers to my domain, DNS is not updated with their IP address and hostname.
This association, or mapping, of an IP address to a domain name requires that a change in either the address or the name necessitates an update of the information in DNS.
The DHCP protocol does not automatically update DNS in the event that the DHCP server changes the IP address of a client.
DNS servers provide domain name resolution for network resources.
They associate the TCP/IP address assigned by DHCP to a client with its fully qualified domain name (FQDN).
Some of the servers will not update the Reverse Lookup zones and as you can imagine spiceworks is upset about this.