No 'MX' Records Found
[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: 2006-05-17
The Microsoft® Exchange Server Analyzer Tool queries the Domain Name System (DNS) servers it uses for the mail exchanger (MX) records of remote domains that Exchange sends to.
If the Exchange Server Analyzer cannot retrieve MX records for a remote domain from the DNS servers it uses, the Exchange Server Analyzer displays a warning.
This warning indicates that the DNS MX records appear to be missing for the remote domain.
To determine mail hosts, the sending Exchange server checks for an MX record. Next, the sending server resolves the MX record to an IP address by checking for an address (A) record.
If MX records for remote domains are missing, this may cause messages destined for the remote domains to back up in the Exchange server Remote Delivery queues in addition to other routing or service delays.
The DNS lookup of the MX records can fail if the DNS server is down or unreachable because of a network failure or for other reasons.
To verify that the DNS server is online and that the MX records are present
Verify that the DNS server is running by doing one or more of the following checks:
Look at the DNS server status from the DNS Administration program on the DNS server.
Restart the DNS server. For more information, see "Start, stop, pause, or restart a DNS server" (http://go.microsoft.com/fwlink/?LinkId=62999).
Verify the DNS server responsiveness by using the nslookup command. For more information, see the instructions in "Verify DNS server responsiveness using the nslookup command" (http://go.microsoft.com/fwlink/?LinkId=63000).
Use nslookup to verify that the MX records are configured correctly. For more information, see "How to Use Nslookup to Verify MX record configuration" in the "Verifying DNS Design and Configuration" section of the Exchange Server Transport and Routing Guide (http://go.microsoft.com/fwlink/?LinkId=47579).
For More Information
For information about how Exchange Server 2003 uses DNS to resolve external IP addresses, see "Transport Dependencies for Exchange Server 2003" in the Exchange Server Transport and Routing Guide (http://go.microsoft.com/fwlink/?LinkId=47579).
For information about DNS name resolution, see Microsoft Knowledge Base article 322856, "How to configure DNS to use with Exchange Server" (http://go.microsoft.com/fwlink/?linkid=3052&kbid=322856).
For information about how to troubleshoot DNS, see "Troubleshooting DNS" (http://go.microsoft.com/fwlink/?LinkId=63003).
For information about Exchange Server 2003 system monitoring, see "Chapter 3: System Monitoring with Exchange Server 2003 Management Pack" in the Exchange Server 2003 Management Pack Guide for MOM 2000 SP1 (http://go.microsoft.com/fwlink/?LinkId=47573).