No DNS Name Resolution If DHCP Client Service Is Not Running

This article was previously published under Q268674
This article has been archived. It is offered "as is" and will no longer be updated.
When you try to resolve a host name using Domain Name Service (DNS), the attempt is unsuccessful. Communication by Internet Protocol (IP) address (even to the DNS server) and the Nslookup utility against the DNS server both work correctly.
The Dynamic Host Configuration Protocol (DHCP) Client Service may not be running.
Start the DHCP Client Service, and then set it to start automatically at startup. To do so, follow these steps:
  1. Right-click the My Computer icon on your desktop, and then click Manage.
  2. In the Computer Management console, double-click Services and Applications, and then click Services.
  3. In the rightmost window, right-click DHCP Client and then click Properties.
  4. Change Startup type to Automatic, and then click OK.
  5. Right-click the DHCP Client service again, and then click Start.
This behavior may occur even if the system is not using DHCP to obtain an IP address; that is, even if the system has a statically configured IP address.

The DHCP Client service is set to start automatically by default in Windows 2000.

The DHCP Client Service is also responsible for registering Dynamic DNS (DDNS) names in Windows 2000.

Important The DHCP client service is required for registration of DNS records computers with DHCP and statically assigned IP addresses.

For additional information about Dynamic DNS and the DHCP Client, click the article numbers below to view the articles in the Microsoft Knowledge Base:
246804 How to Enable/Disable Windows 2000 Dynamic DNS Registrations
264539 Dynamic DNS Updates Do Not Work After Stopping the DHCP Client Service

Article ID: 268674 - Last Review: 12/05/2015 21:04:55 - Revision: 3.4

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition

  • kbnosurvey kbarchive kbdhcp kbprb KB268674