Name Resolution Problems Occur When You Try to Access a Domain Controller by Using Its Alternate Computer Name

After you add an alternate computer name to a domain controller that is running Microsoft Windows Server 2003, you later experience Domain Name System (DNS) name resolution problems when you try to access that server by using its alternate name. If you restart the server, the problem is temporarily resolved.

This problem occurs if the server where you configured the alternate name is configured to dynamically register its name in DNS. The primary name of the server is updated in DNS at the interval that is specified in the DefaultRegistrationRefreshInterval value. However, the alternate computer name is not updated. As a result, the DNS record for this alternate computer name is eventually scavenged (if aging and scavenging is enabled), and you experience problems when you try to access the server or the services that are hosted on the server. When you restart the server computer, both the primary and alternate computer names are again registered in DNS.

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

No prerequisites are required.

Restart Requirement

You must restart the computer to apply the changes after you install this hotfix. However, you do not have to restart the computer immediately after the hotfix installation is complete.

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) 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 tool in Control Panel.

Windows Server 2003, 32-Bit Editions

Windows Server 2003, 64-Bit Edition

To work around this problem, configure a static host (A) record for the alternate computer name of the domain controller.

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

You can add an alternate computer name by using the Netdom.exe command. This command is included with the Microsoft Windows Server 2003 Support Tools. To install the Windows Server 2003 Support Tools, right-click Suptools.msi in the Support\Tools folder on the Windows Server 2003 CD-ROM, and then click Install.

For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base: