Event ID 11050 — DNS Client Service Status

Updated: November 13, 2007

Applies To: Windows Server 2008

yellow

Domain Name System (DNS) is a protocol that makes it possible for a computer to obtain the numeric IP address of another computer by submitting the target computer's name to a DNS server computer. The DNS Client service sends requests for name resolution services to DNS servers. Problems with the DNS Client service can prevent a network computer from locating other network computers.

Event Details

Product: Windows Operating System
ID: 11050
Source: DnsApi
Version: 6.0
Symbolic Name: EVENT_DNS_CACHE_NETWORK_PERF_WARNING
Message: The DNS Client service could not contact any DNS servers after repeated attempts. To avoid further network performance problems, the DNS Client service will not use the network for %3 seconds, after which it will resume its normal behavior. If this problem persists, check that this computer is configured to use a preferred (and possibly an alternate) DNS server. If the problem continues after you have configured the computer to use a DNS server, verify that the DNS server can be accessed, or contact your network administrator.

Resolve

Configure a preferred DNS server

Check that this computer is configured to use a preferred, and possibly an alternate, DNS server. If the problem continues after you have configured the computer to use a DNS server, confirm that the DNS server can be accessed.

Before you perform this procedure, you must determine whether your network is configured to provide a DNS server address automatically and, if not, the address of your computer's DNS server.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To configure TCP/IP DNS server settings:

  1. On the DNS client computer, click Start, and then click Control Panel.
  2. Click Control Panel Home, and then click View Network Status and Tasks.
  3. Under the network connection, click View status, and then click Properties.
  4. Click Internet Protocol Version 4 (TCP/IPv4), and then click Properties.
  5. Do one of the following:
    • If your network is configured to provide a DNS server address automatically, click Obtain a DNS server address automatically.
    • If your network is not configured to provide a DNS server address automatically, click Use the following DNS server addresses, and then, in Preferred DNS server, type the address of the assigned DNS server. If you have the address of a second DNS server, type that address in Alternate DNS server.
  6. Click OK to close the dialog box.
  7. Click Internet Protocol Version 6 (TCP/IPv6), and then click Properties.
  8. Do one of the following:
    • If your network is configured to provide a DNS server address automatically, click Obtain a DNS server address automatically.
    • If your network is not configured to provide a DNS server address automatically, click Use the following DNS server addresses, and then, in Preferred DNS server, type the address of the assigned DNS server. If you have the address of a second DNS server, type that address in Alternate DNS server.
  9. Click OK to close all dialog boxes.

Use the ipconfig and ping commands to confirm that the DNS server can be accessed.

To use the ipconfig and ping commands to confirm DNS server availability:

  1. On the DNS client computer, open a command prompt. To open a command prompt, click Start, click All Programs, click Accessories, and then click Command Prompt.
  2. Type ipconfig /all, press ENTER, and then note the addresses next to DNS Server.
  3. For each address, type ping <address>, and then press ENTER.

The command output should indicate that one or more of the DNS servers replied to the command. If not, the problem is most likely caused by network connectivity problems.

For more information about how to troubleshoot network connectivity problems, see article 325487 in the Microsoft Knowledge Base (http://go.microsoft.com/fwlink/?LinkID=46059).

Verify

Check the event log, and verify that there are no DNS client events in the Event ID range 11000 through 11007.

Check that the following events exist for the domain name that is being used for the DNS client:

  • Event ID 11200
  • Event ID 11201
  • Event ID 11202

Related Management Information

DNS Client Service Status

DNS Infrastructure

Community Additions

ADD
Show: