Dynamic DNS updates do not work if the DHCP client service stops

The client computer does not send dynamic Domain Name System (DNS) updates to the DNS server even though the Register this connection's address in DNS option is selected.

You receive the following error forcing DNS registration: Additionally, you may receive the following error message when you try to use the netdiag /fix command to correct DNS registration problems:

Dynamic DNS registration relies on the Dynamic Host Configuration Protocol (DHCP) client service to perform dynamic updates. When you disable or set the DHCP client service to start manually, it prevents dynamic DNS updates from occurring. Even if the client or server uses a static Internet Protocol (IP) address, the DHCP client service must be running for dynamic DNS updates to occur.

To resolve this issue, you must configure the DHCP client service to start automatically when your computer system starts.

This behavior is by design.

If you require DNS names to be immediately registered, the DHCP client service can be restarted immediately. To do this, type the following command: To ensure that all names are correctly registered when you restart of the DHCP client service, you should type the ipconfig command with the registerdns option: If your computer is a domain controller, you must manually stop and restart NetLogon service. To do this, type the following commands: For more information on the DNS Client service and dynamic updates please refer to the Windows 2000 DNS white paper, which is available at the Microsoft Web site: Also, in the Windows 2000 Server, you can locate information in Help. To do so, click Start, click Help, on the Index tab navigate to "DNS dynamic updates, overview" and then to a section entitled "Example: How dynamic update works."

Note If the DHCP client service is not running on a Windows 2000 Advanced Server MSCS cluster node you may also see the following warning in the system event log: