DHCP clients may take a long time to register their names on a DNS server that is running Windows Server 2003

Dynamic Host Configuration Protocol (DHCP) clients may take a long time to register their names on a Domain Name System (DNS) server that is running Microsoft Windows Server 2003. DHCP client names cannot be resolved until their names are successfully registered on a DNS server. Applications that rely on name solution may stop working because of name resolution failure.

This problem occurs if the following conditions are true:

• A centralized DNS server is configured on a Wide Area Network (WAN). This DNS server owns all DNS zones.
• Some local cached DNS servers are configured on the local area network (LAN).
• One or more local DNS servers are configured for every DHCP scope.
• Many DHCP renewal requests occur because the DHCP clients roam aggressively.

For every DHCP renewal request, the DHCP server puts the name registration request of the DHCP client in a queue. Then, the DHCP server handles the requests one by one. When the DHCP server handles the DHCP client request, the DHCP server has to contact both a local DNS server and the centralized DNS server. This is because the local DNS server does not own DNS zones for every request. Therefore, unnecessary network traffic occurs over the WAN. This traffic delays the resolution of DHCP client requests. If the volume of the DHCP requests is large, it takes a long time for some DHCP clients to register their names.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

Microsoft Windows Server 2003 Service Pack 1 (SP1) or Windows Server 2003 Service Pack 2 (SP2)and the DHCP component must be installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 with SP1, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 with SP1, Itanium-based versions

Windows Server 2003 with SP2, x86-based versions

Windows Server 2003 with SP2, x64-based versions

Windows Server 2003 with SP2, Itanium-based versions

Post-installation instructions

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
After you install this hotfix, you must create the AlternateDnsServer registry key. After you do this, the DHCP server will directly send name registration requests to the correct DNS servers. Network traffic over the WAN decreases. Therefore, the performance of the DHCP server improves.

To create the AlternateDnsServer registry key, follow these steps:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then double-click the following registry subkey:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\DHCPServer\Parameters
3. On the Edit menu, point to New, and then click Key.
4. Type AlternateDnsServer, and then press ENTER.
5. Right-click AlternateDnsServer, click New, and then click String Value.
6. Type IP_ADDRESS as the name of the registry entry, and then press ENTER. Double-click IP_ADDRESS, and then type the IP address of the other DNS server in the Value data box.
7. On the File menu, click Exit to close Registry Editor.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.