Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

When you run the "Ipconfig /displaydns" command in Windows Server 2003, the results are incomplete


View products that this article applies to.

Symptoms

In Microsoft Windows Server 2003, you run the ipconfig /displaydns command to display the content of the DNS resolver cache. However, the results are incomplete. When this problem occurs, you do not receive a message.

This problem occurs if there are too many entries in the DNS resolver cache. Typically, this problem occurs when there are too many custom entries in the Hosts file.

↑ Back to the top


Cause

This problem occurs when an allocated buffer is not large enough to contain all the contents of the DNS resolver cache. When the Ipconfig.exe tool allocates memory, it does not consider the DNS entries in the Hosts file.

↑ Back to the top


Resolution

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

To apply this hotfix, you must have one of the following operating systems installed:
  • Windows Server 2003 Service Pack 2
  • Windows Server 2003 Service Pack 1
  • An x64-based version of Windows Server 2003
For more information about how to obtain the latest service pack, 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.

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 2, 32-bit (x86-based) versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipconfig.exe5.2.3790.405263,48802-Apr-200711:52x86SP2SP2QFE
Windows Server 2003 with Service Pack 2, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipconfig.exe5.2.3790.405285,50402-Apr-200715:49x64SP2SP2QFE
Wipconfig.exe5.2.3790.405263,48802-Apr-200715:49x86SP2WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipconfig.exe5.2.3790.4052130,04802-Apr-200715:48IA-64SP2SP2QFE
Wipconfig.exe5.2.3790.405263,48802-Apr-200715:48x86SP2WOW
Windows Server 2003 with Service Pack 1, 32-bit (x86-based) versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipconfig.exe5.2.3790.291063,48802-Apr-200711:14x86SP1SP1QFE
Windows Server 2003, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipconfig.exe5.2.3790.291085,50402-Apr-200715:45x64SP1SP1QFE
Wipconfig.exe5.2.3790.291063,48802-Apr-200715:45x86SP1WOW
Windows Server 2003 with Service Pack 1, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Ipconfig.exe5.2.3790.2910130,04802-Apr-200715:45IA-64SP1SP1QFE
Wipconfig.exe5.2.3790.291063,48802-Apr-200715:45x86SP1WOW

↑ Back to the top


Status

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

↑ Back to the top


More information

For more information about DNS resolution and the Hosts file, visit the following Microsoft TechNet Web site: For more information about the terms that are used to describe software updates, 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

↑ Back to the top


Keywords: kbautohotfix, kbexpertiseinter, kbwinserv2003postsp2fix, kbbug, kbfix, kbHotfixServer, kbqfe, KB934401

↑ Back to the top

Article Info
Article ID : 934401
Revision : 2
Created on : 10/8/2011
Published on : 10/8/2011
Exists online : False
Views : 289