How Windows 2000 DHCP Updates DNS Records

In Microsoft Windows 2000, the DHCP Server service plays a critical role in maintaining network name resolution by synchronizing IP address leases with Domain Name System (DNS) records. By integrating Dynamic Host Configuration Protocol (DHCP) with Dynamic DNS (DDNS), the Windows 2000 DHCP server automates the registration, modification, and deletion of pointer (PTR) and address (A) resource records. This interaction ensures hostnames remain accurate as IP leases change, bridges legacy operating systems that lack native dynamic update capabilities, and reduces administrative overhead.

Dynamic DNS Integration Overview

Prior to Windows 2000, DNS required manual administration or proprietary synchronization mechanisms. Windows 2000 introduced support for RFC 2136 (Dynamic Updates in the Domain Name System). When a client obtains or renews an IP lease, the DHCP service can interact directly with a dynamic-capable DNS server to register or update the client's Fully Qualified Domain Name (FQDN) and associated IP address.

Default Update Behavior

By default, the division of labor between Windows 2000 clients and the Windows 2000 DHCP server is split based on record type:

  • Client Responsibilities: A native Windows 2000 client directly updates its own forward lookup record (Host or A record) with the DNS server.
  • DHCP Server Responsibilities: The DHCP server registers the reverse lookup record (Pointer or PTR record) on behalf of the client once the lease is granted.

This coordination is negotiated via DHCP Option 81 (the Client FQDN option), which allows the client and server to agree on who will perform the A and PTR record updates.

Support for Down-Level Clients

Legacy operating systems—such as Windows NT 4.0, Windows 95, and Windows 98—do not possess native Dynamic DNS client services. The Windows 2000 DHCP Server service resolves this limitation by acting as a dynamic update proxy. When configured to update DNS for clients that do not support dynamic updates, the DHCP server handles the registration of both the forward (A) and reverse (PTR) records on behalf of these legacy machines.

Configurable Update Modes

Administrators can modify the DHCP server properties to alter how it handles dynamic DNS updates:

  1. Update DNS only if requested by the DHCP client: Follows the standard negotiation process where the client dictates update delegation.
  2. Always dynamically update DNS A and PTR records: Forces the DHCP server to register both the forward and reverse records for every client, overriding any client-side preference.
  3. Discard forward and reverse lookups when lease is deleted: Instructs the DHCP server to automatically delete the associated A and PTR records from DNS when an IP address lease expires or is released, preventing stale DNS data.
  4. Enable updates for clients that do not support Dynamic DNS: Ensures older systems are still indexed properly in the DNS zone.

Security and Record Ownership (DnsUpdateProxy Group)

In environments using Active Directory-integrated DNS zones with secure dynamic updates enabled, record ownership determines who can modify or delete a DNS record. If a DHCP server creates a record on behalf of a client, the DHCP server machine account becomes the owner of that record.

To prevent issues where multiple DHCP servers cannot update each other's records, or where an upgraded client cannot take ownership of its own record, Windows 2000 provides the DnsUpdateProxy security group. Any DHCP server placed in this group creates DNS records without security restrictions (an unauthenticated Access Control List), allowing subsequent clients or replacement DHCP servers to take over ownership and update the record securely.