Microsoft KB Archive/945980

= DNS name resolution does not work on Windows Server 2003 =

Article ID: 945980

Article Last Modified on 12/5/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-



Source: Microsoft Support



RAPID PUBLISHING
RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.



Action


Result
On the Windows Server 2003 computer, you are unable to perform DNS name resolution. You may experience the following issues:

Ping www.microsoft.com, you get a “host not found” error.

If you create a hosts file and put the record into the hosts file, the same issue occurs.

If you use the NSLOOKUP tool to query the record, it may work.

If you collect a Network Monitor trace, you find that there is no DNS packet coming out from the computer.

If you Ping localhost, it fails too.

When the problem happens, the DNS Client Service is up and running.

Clearing the DNS resolver cache, IP Reset, Winsock Reset may not help.



Cause
This problem may occur if the following registry values were deleted.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

&quot;Domain&quot;=&quot;&quot;

&quot;NV Domain&quot;=&quot;&quot;

This may happen If the Windows Server 2003 computer is imaged using the some imaging software.



Resolution
Create these two REG_SZ values. If the computers are members of a Windows 2003 domain, by default these two values should be the Domain DNS name.

1. Launch Registry Editor and locate the following key.

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

2. In the right pane, find these two REG_SZ values:

&quot;Domain&quot;

&quot;NV Domain&quot;

If the values do not exist, manually create them.

3. Modify the data of these two values so that they are the DNS name of the domain. For example, if the domain is named mydomain.com, then the data of these two values should be mydomain.com too.

4. Exit Registry Editor and reboot the computer.



DISCLAIMER
MICROSOFT CORPORATION AND/OR ITS RESPECTIVE SUPPLIERS MAKE NO REPRESENTATIONS ABOUT THE SUITABILITY, RELIABILITY, OR ACCURACY OF THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN. ALL SUCH INFORMATION AND RELATED GRAPHICS ARE PROVIDED &quot;AS IS&quot; WITHOUT WARRANTY OF ANY KIND. MICROSOFT AND/OR ITS RESPECTIVE SUPPLIERS HEREBY DISCLAIM ALL WARRANTIES AND CONDITIONS WITH REGARD TO THIS INFORMATION AND RELATED GRAPHICS, INCLUDING ALL IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, WORKMANLIKE EFFORT, TITLE AND NON-INFRINGEMENT. YOU SPECIFICALLY AGREE THAT IN NO EVENT SHALL MICROSOFT AND/OR ITS SUPPLIERS BE LIABLE FOR ANY DIRECT, INDIRECT, PUNITIVE, INCIDENTAL, SPECIAL, CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF USE, DATA OR PROFITS, ARISING OUT OF OR IN ANY WAY CONNECTED WITH THE USE OF OR INABILITY TO USE THE INFORMATION AND RELATED GRAPHICS CONTAINED HEREIN, WHETHER BASED ON CONTRACT, TORT, NEGLIGENCE, STRICT LIABILITY OR OTHERWISE, EVEN IF MICROSOFT OR ANY OF ITS SUPPLIERS HAS BEEN ADVISED OF THE POSSIBILITY OF DAMAGES.

Keywords: kbnomt kbrapidpub KB945980

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.