Troubleshoot DNS Problems Related to Active Directory

Cc526683.chm_head_left(en-us,TechNet.10).gif Cc526683.chm_head_middle(en-us,TechNet.10).gif Cc526683.chm_head_right(en-us,TechNet.10).gif

Troubleshoot DNS Problems Related to Active Directory

Active Directory functionality depends on the proper configuration of the DNS infrastructure. This includes the following:

  • DNS client configuration, including domain controllers, domain members, and other computers.
  • DNS server and zone configuration and proper delegations in parent DNS zones.
  • Presence of DNS domain controller locator records.

DNS Records Required for Proper Active Directory Functionality

Following the best practice recommendations regarding DNS configuration from the beginning of the deployment is key for successful Active Directory deployment and operations. Before troubleshooting problems related to DNS, it is important to understand what DNS records are required for proper Active Directory functionality.

The following table lists the DNS records that are required for proper Active Directory functionality.

Table: Required DNS Records

Mnemonic Type DNS record Requirements
Pdc SRV _ldap._tcp.pdc._msdcs.<DnsDomainName> One per domain.
GC SRV _ldap._tcp.gc._msdcs.<DnsForestName> At least one per forest.
DsaCname CNAME <DsaGuide>._msdcs.<DnsForestName> One per domain controller.
Kdc SRV _kerberos._tcp.dc._msdcs.<DnsDomainName> At least one per domain.
Dc SRV _ldap._tcp.dc._msdcs.<DnsDomainName> At least one per domain.
- A <DomainControllerFQDN> One per domain controller. (Domain controllers that have multiple IP addresses can have more than one "A" resource record.)

Common Events and Symptoms That Indicate DNS Problems

The following table lists the common events and symptoms that indicate DNS problems and their solutions.

Table: Common Events That Indicated DNS Problems

Event or symptom Root cause Solution
Netlogon Event ID 5774 The domain controller cannot dynamically register DNS records that advertise its availability as a domain controller. Troubleshoot domain controller locator DNS records registration failure.
Netlogon Event ID 5775 The domain controller cannot dynamically register DNS records that advertise its availability as a domain controller. Troubleshoot domain controller locator DNS records registration failure.
Netlogon Event ID 5781 The domain controller cannot dynamically register DNS records that advertise its availability as a domain controller. Troubleshoot domain controller locator DNS records registration failure.
Netlogon Event ID 5783 The source server listed in the error message was unable to complete a remote procedure call (RPC) call to the destination server. Most commonly, this means that either the source server could not locate the server in DNS or the RPC interface on the destination server is not working. If the source server could not locate the server in DNS, troubleshoot Active Directory replication failure due to incorrect DNS configuration. If this is not a DNS problem, troubleshoot RPC problems.
Active Directory Installation Wizard failed because it was unable to locate a domain controller. In order to add a server to an existing forest, the Active Directory Installation Wizard must be able to find a domain controller in the domain or the forest. Troubleshoot Active Directory Installation Wizard failure to locate domain controller.
Unable to join a domain. The failure might be due to being unable to locate a domain controller, which usually indicates DNS problems. Troubleshoot failure to locate domain controller when attempting to join a domain.

Domain Controller Locator DNS Records Registration Failure

In this procedure, you verify that in the IP configuration the specified DNS servers are correct.

Procedure DRX.6: To troubleshoot domain controller locator DNS records registration failure

  1. Verify network configuration to ensure that the preferred and alternate DNS servers specified in the IP configuration of the domain controller are correct.
  2. At a command prompt, press ENTER after typing the following command:<pre IsFakePre="true" xmlns="http://www.w3.org/1999/xhtml">dcdiag /test:registerindns /dnsdomain:FQDN /v</pre>
  3. Follow the recommendations provided in the output.