Export (0) Print
Expand All
Expand Minimize
7 out of 26 rated this helpful - Rate this topic

The Host Name Could Not be Resolved in DNS

 

Topic Last Modified: 2011-11-09

The Microsoft Analyzer Tool performs a Domain Name System (DNS) lookup to retrieve the Host (A) record of the host name provided. If the DNS lookup operation does not return an IP address, then the Exchange Remote Connectivity Analyzer displays the following error message:

"The host name could not be resolved in DNS."

To correct this error, do the following.

  • Use nslookup to verify that the Host (A) record exists on the DNS server. For more information, see To verify A resource records exist in DNS.
  • If the Host (A) resource record does not exist or is incorrect, then manually add or modify the host record. If your external DNS zone is hosted by a third party, you may have to contact that company or use custom tools to make these DNS modifications.

For information about how to troubleshoot DNS, see Troubleshooting DNS.

The Exchange Remote Connectivity Analyzer is a new tool with limited documentation at this time. In an effort to improve the documentation for each of the errors you might receive, we would like to solicit additional information from the community. Please use the Community Content section below to post additional reasons why you failed at this point. If you need technical assistance, please create a post in the appropriate Exchange TechNet forum or contact support.

Sometimes, you may have to verify the URL that is used for the AD FS endpoint for Office 365 identity federation. For a procedure to determine the value to which the endpoint is currently set, see the “More Information” section of Internet Explorer cannot display the Office 365 portal webpage when a federated user tries to sign in.

 
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.