Exchange Connection Problems

Fix Exchange Online DNS A and MX Record Errors

Algirdas JasaitisAlgirdas Jasaitis Nov 14, 2026 868 views

Question details

The user needs to identify and correct DNS issues that may prevent Exchange Online email delivery.

Fix Exchange Online DNS A and MX Record Errors
Product
Microsoft Exchange Online
Device & OS
not provided
Scenario
Email delivery fails with a host or domain name not found error, potentially because of incorrect DNS records or a domain provider issue.
Observed behavior
A delivery error indicates that a host or domain name could not be found.
Before you start

Find the complete delivery error and identify the domain or host named in it. Have access to the Microsoft 365 admin center and the domain's authoritative DNS provider, or contact the relevant administrators.

Solution 1Recommended

Verify the domain's MX and A records

Use this approach when delivery errors point to a domain managed by your organization.

1
Check the delivery error

Open the nondelivery report and identify the domain or host that could not be found. If it belongs to the recipient, ask the recipient's administrator to check its DNS records.

2
Find the expected MX record

In the Microsoft 365 admin center, go to Settings > Domains, select your domain, and review its DNS records. Note the MX destination shown for Exchange Online.

3
Compare the published records

Use a DNS lookup tool or run `nslookup -type=mx example.com`, replacing example.com with your domain. Compare the result with the MX destination shown in the admin center. Look up any host named in the error with `nslookup -type=a hostname`.

4
Correct records at the DNS host

Sign in to the authoritative DNS provider's dashboard and open the domain's DNS management page. Correct an invalid A record if it is involved in the error, and update the MX record to the Microsoft 365 destination if Exchange Online should receive the domain's mail.

5
Check again

After saving changes, repeat the DNS lookup and send a test email. Allow time for DNS changes to propagate according to the records' cache settings.

Verify the domain's MX and A records
Avoid unrelated DNS changes: Do not remove an A record solely because mail is failing; it may support a website or another service. If your organization uses a third-party mail gateway, confirm the intended MX routing before changing it.
Free Microsoft Office alternative

Work with Office files in WPS Office

WPS Office is a free, lightweight alternative for everyday document, spreadsheet, and presentation work. Its familiar interface and Microsoft Office format support make it easy to move existing files. It does not repair Exchange Online DNS or email routing.

Keep working on office files while an administrator resolves mail deliveryOpen and edit Microsoft Office DOCX, XLSX, and PPTX filesUse a familiar interface for documents, spreadsheets, and presentationsMove existing Office files into a lightweight, free productivity suite
microsoft office alternative - wps office

Frequently Asked Questions

Where can I find the correct MX record for Exchange Online?

In the Microsoft 365 admin center, go to Settings > Domains, select your domain, and review its DNS records. Compare the displayed MX destination with the record published by your DNS host.

Does an email delivery error mean I should delete the domain's A record?

No. An A record may serve a website or another service. Check whether the host named in the delivery error has an invalid A record, and correct it only if you understand its role.

What if the failed domain belongs to the recipient?

Share the nondelivery report with the recipient or their email administrator. They need to check their domain's DNS and mail routing; you generally cannot change their records.

What should I do if I cannot access the DNS provider account?

Contact the registrar or authoritative DNS host through its support portal. Provide the affected domain, the complete delivery error, and the account-access details needed to investigate.