Renew DNS client registration using the ipconfig command
Applies To: Windows Server 2003, Windows Server 2003 R2, Windows Server 2003 with SP1, Windows Server 2003 with SP2
To renew DNS client registration using the ipconfig command
Open Command Prompt.
The name of the command-line program.
The command to renew DNS client registration.
Performing this task does not require you to have administrative credentials. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.
To open a command prompt, click Start, point to All programs, point to Accessories, and then click Command prompt.
To view the complete syntax for this command, at a command prompt, type:
An additional command to /registerdns is to 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.
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 restarting the client.
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 on computers running Windows 2000, Windows XP, or Windows Server 2003 operating systems.
On computers running Windows 2000, Windows XP, or Windows Server 2003 operating systems, 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:
The zone where the client requires update or registration is not able to accept dynamic updates.
The DNS servers that the client is configured to use do not support or recognize the DNS dynamic update protocol.
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.
The server or zone is not available because of other problems, such as a network or server failure.
Information about functional differences
- Your server might function differently based on the version and edition of the operating system that is installed, your account permissions, and your menu settings. For more information, see Viewing Help on the Web.