Was this page helpful?
Additional feedback?
1500 characters remaining
Export (0) Print
Expand All
Collapse the table of content
Expand the table of content
Expand Minimize

Directory Server DNS name resolution failure

[This topic is intended to address a specific issue called out by the Exchange Server Analyzer Tool. You should apply it only to systems that have had the Exchange Server Analyzer Tool run against them and are experiencing that specific issue. The Exchange Server Analyzer Tool, available as a free download, remotely collects configuration data from each server in the topology and automatically analyzes the data. The resulting report details important configuration issues, potential problems, and nondefault product settings. By following these recommendations, you can achieve better performance, scalability, reliability, and uptime. For more information about the tool or to download the latest versions, see "Microsoft Exchange Analyzers" at http://go.microsoft.com/fwlink/?linkid=34707.]  

Topic Last Modified: 2009-09-23

The Microsoft® Exchange Server Analyzer Tool attempts a Domain Name System (DNS) query against the configured DNS servers for each Active Directory® directory service server. This connection is made by using a custom object processor that performs a name resolution request and analyzes the results. If the Exchange Server Analyzer does not receive an IP address as part of the query results, an error is displayed.

This error indicates that a directory server was not found in DNS. Both Exchange Server and Active Directory require correctly configured and healthy DNS to operate correctly. DNS registration and resolution issues can have widespread effects on the ability to send, receive, and deliver messages.

You must configure DNS correctly to ensure that Active Directory and Exchange Server will function correctly. For a more in-depth treatment of DNS configuration for Active Directory, see the Microsoft Knowledge Base article 237675, "Setting Up the Domain Name System for Active Directory" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=237675).

  1. Review the following configuration items to ensure that DNS is healthy and that the Active Directory DNS entries will be registered correctly:

    • DNS IP configuration

    • Dynamic zone updates

    • DNS forwarders

  2. Check for the existence of a Root Zone entry. View the Forward Lookup zones in the DNS Management console. There should be an entry for the domain. Other zone entries may exist. There should not be a dot (".") zone. If the dot (".") zone exists, delete the dot (".") zone. The dot (".") zone identifies the DNS server as a root server. Typically, an Active Directory domain that needs external (Internet) access should not be configured as a root DNS server. Manually reregister the directory server IP address using Ipconfig /registerdns on the directory server after you delete the dot ("."). The Netlogon service may also need to be restarted.

  3. Manually repopulate Active Directory DNS entries using netdiag /fix on the directory server.

For more information about using DNS with Active Directory, see the Microsoft Knowledge Base article 323418, "How To Integrate DNS with an Existing DNS Infrastructure If Active Directory Is Enabled in Windows Server 2003" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=323418).

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

© 2015 Microsoft