Microsoft KB Archive/933284

From BetaArchive Wiki
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

Article ID: 933284

Article Last Modified on 10/11/2007



APPLIES TO

  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems



SYMPTOMS

In Microsoft Windows Server 2003, you try to resolve a Domain Name System (DNS) name by using entries in the Hosts file. When you do this, the DNS name resolution may fail. Typically, this problem occurs when the DNS Client service is busy or when the DNS Client service stops.

CAUSE

When the DNS Client service is busy or when the DNS Client service stops, the querying application resolves the DNS name by using the DNS API. However, the DNS API sets an incorrect flag on the DNS record. The DNS API sets the incorrect flag when the DNS record that is retrieved from the Hosts file is returned by the DNS API. The incorrect flag causes the querying application to discard the DNS record.

RESOLUTION

If this problem occurs when the DNS Client service stops, resolve this problem by starting the DNS Client service. Otherwise, apply the hotfix that is described in this article.

To start the DNS Client service, run the following command at a command prompt:

Net Start DNSCache


Hotfix information

A supported hotfix is now 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 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003


Restart requirement

You do not have to restart the computer after you apply this hotfix. Instead, restart the affected application only.

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 Service Pack 1, x86-based versions
File name File version File size Date Time Platform
Dnsapi.dll 5.2.3790.2936 157,696 15-May-2007 06:49 x86
Windows Server 2003 with Service Pack 2, x86-based versions
File name File version File size Date Time Platform
Dnsapi.dll 5.2.3790.4080 160,256 15-May-2007 06:36 x86
Windows Server 2003 with Service Pack 1, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Dnsapi.dll 5.2.3790.2936 437,760 14-May-2007 16:43 IA-64 SP1 Not Applicable
Wdnsapi.dll 5.2.3790.2936 157,696 14-May-2007 16:43 x86 SP1 WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
File name File version File size Date Time Platform SP requirement Service branch
Dnsapi.dll 5.2.3790.4080 437,760 14-May-2007 16:44 IA-64 SP2 Not Applicable
Wdnsapi.dll 5.2.3790.4080 160,256 14-May-2007 16:44 x86 SP2 WOW
Windows Server 2003, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Dnsapi.dll 5.2.3790.2936 305,664 14-May-2007 16:36 x64 SP1 Not Applicable
Wdnsapi.dll 5.2.3790.2936 157,696 14-May-2007 16:36 x86 SP1 WOW
Windows Server 2003 with Service Pack 2, x64-based versions
File name File version File size Date Time Platform SP requirement Service branch
Dnsapi.dll 5.2.3790.4080 305,664 14-May-2007 16:43 x64 SP2 Not Applicable
Wdnsapi.dll 5.2.3790.4080 160,256 14-May-2007 16:43 x86 SP2 WOW


STATUS

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

MORE INFORMATION

During the DNS name resolution, the system searches for DNS records in the Hosts file. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

172218 Microsoft TCP/IP host name resolution order


For more information about DNS record flags, visit the following Microsoft Web site:

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



Additional query words: dnsapi DNSREC_ANSWER

Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB933284