Name Resolution Problems Occur When You Try to Access a Domain Controller by Using Its Alternate Computer Name (824147)
The information in this article applies to:
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, 64-Bit Enterprise Edition
SYMPTOMSAfter 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. CAUSEThis 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.RESOLUTIONHotfix InformationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. PrerequisitesNo prerequisites are required. Restart RequirementYou 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 InformationThis hotfix does not replace any other hotfixes. File InformationThe 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 Date Time Version Size File name
-----------------------------------------------------
12-Feb-2004 14:30 5.2.3790.127 151,552 Dnsapi.dll
Windows Server 2003, 64-Bit Edition Date Time Version Size File name Platform
--------------------------------------------------------------
12-Feb-2004 12:30 5.2.3790.127 415,744 Dnsapi.dll IA-64
12-Feb-2004 12:30 5.2.3790.127 151,552 Wdnsapi.dll x86
WORKAROUNDTo work around this problem, configure a static host (A) record for the alternate computer name of the domain controller.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Modification Type: | Minor | Last Reviewed: | 10/27/2005 |
---|
Keywords: | kbHotfixServer kbQFE kbBug kbfix kbQFE kbWinServ2003preSP1fix KB824147 kbAudITPRO |
---|
|