To renew DNS client registration using the ipconfig command

• At a command prompt, type:

  ipconfig /registerdns

  Or, type ipconfig /registerdns [adapter]

  Where adapter is the name of a specific network adapter installed on the computer for which you want to renew or update registrations.

 Note

• To open a command prompt, click Start, point to Programs, point to Accessories, and then click Command Prompt.
• The ipconfig /registerdns command provides you with a means to manually initiate dynamic registration for the DNS names and IP addresses configured at a computer. This option can assist in troubleshooting a failed DNS name registration or in resolving a dynamic update problem between a client and the DNS server without requiring a client reboot.
• By default, the ipconfig /registerdns command refreshes all DHCP address leases and registers all related DNS names configured and used by the client computer.
• To learn the names of adapters that you can optionally specify with this command, first type the ipconfig command by itself (that is, do not specify any additional parameters). The command output displays all adapters by name that are available for use at the computer.
• Although the ipconfig command is provided for earlier versions of Windows, the /registerdns option is only available for use at computers running Windows 2000 with the DHCP Client service started.
• For Windows 2000, the DHCP Client service is used to perform dynamic registrations and updates, regardless of whether the computer uses a DHCP server or static configuration to obtain its IP address.
• If you are troubleshooting a failed DNS dynamic registration for a client computer and its DNS names, it might help to verify that the cause is not related to one of the following commonly known causes for such failures:
  1. The zone where the client requires update or registration is not able to accept dynamic updates.
  2. The DNS servers that the client is configured to use do not support or recognize the DNS dynamic update protocol
  3. The primary (or directory-integrated) DNS server for the zone refused the update request. This can most likely occur because the client is not permitted under current zone or resource records security sufficient access rights to update its own name.
  4. The server or zone is not available because of other problems, such as a network or server failure.

Dynamic update

Allow dynamic updates

Modify security for a directory integrated zone

Modify security for a resource record

Allow only secure dynamic updates

Troubleshoot dynamic updates

Ipconfig