Email Migration

How to Fix Exchange Migration Internal Mail Delivery DNS Error 451

Emma Brown Oct 10, 2026 869 views

Question details

Internal messages are stuck in the queue with a DNS query failure error during an Exchange Server migration.

How to Fix Exchange Migration Internal Mail Delivery Failure (DNS Error 451)

Product: Microsoft Exchange Server
Device & OS: not provided
Scenario: Migrating mailboxes from Exchange 2013 to Exchange 2019.
Observed behavior: Internal messages remain queued on the old Exchange server and fail with '451 4.4.0 DNS Query failed' when routing to the new mailbox database.

Before you start

Ensure you have administrative access to both the legacy Exchange 2013 and the new Exchange 2019 servers, and verify that your internal DNS services are functioning normally.

Solution 1Recommended

Verify Internal DNS and Network Adapter Settings

Use this solution to confirm that the old Exchange server can correctly resolve the hostname of the new Exchange server.

The most common cause of the '451 4.4.0' error during a migration is that the sending server cannot resolve the destination server's FQDN. Exchange heavily relies on DNS for internal mail routing.

Check network adapter DNS

Open Network Connections on the Exchange 2013 server, check IPv4 properties, and ensure the primary DNS server points to your internal Domain Controller.

Perform an nslookup

Open Command Prompt as an administrator and type 'nslookup <FQDN of Exchange 2019>'. Ensure it returns the correct internal IP address.

Restart transport service

Open the Exchange Management Shell and run 'Restart-Service MSExchangeTransport' to flush cached routing and DNS configurations.

Verify Internal DNS and Network Adapter Settings

Hosts File Check: If DNS is correct but routing still fails, check the local 'hosts' file (C:\Windows\System32\drivers\etc\hosts) on the old server to ensure there are no outdated or conflicting entries for the new server.

Solution 2

Consult Microsoft Q&A for Advanced Troubleshooting

If standard DNS troubleshooting does not resolve the routing failure, consult Microsoft engineers specializing in Exchange Server migrations.

Free Microsoft Office alternative

Looking for a Lightweight Alternative to Microsoft Office?

Server migrations can be complex and time-consuming. While dealing with Exchange configurations, ensure your team's desktop productivity remains uninterrupted with WPS Office, a free, lightweight, and highly compatible alternative to Microsoft Office.

1. Download WPS Office: Visit the official WPS website and download the free installation package for your operating system.
2. Install the software: Run the installer and follow the on-screen instructions to set up the office suite.
3. Open Office files: Instantly open, edit, and save your existing Word, Excel, and PowerPoint documents without formatting issues.

Fully compatible with Microsoft Office formats including .docx, .xlsx, and .pptxLightweight software that uses minimal system resourcesFamiliar, tabbed user interface for a zero-learning-curve transitionIntegrated PDF tools and cloud storage features

microsoft office alternative - wps office

Frequently Asked Questions

What causes the '451 4.4.0 DNS Query failed' error during Exchange migration?

This error typically occurs when the legacy Exchange server cannot resolve the IP address of the new server due to incorrect DNS settings, missing internal DNS records, or a misconfigured hosts file.

Do I need to restart any services after changing Exchange DNS settings?

Yes, after updating DNS configurations on an Exchange server, you should restart the Microsoft Exchange Transport service so the changes take effect immediately.

Where can I find the exact mail queue error logs?

You can use the Exchange Toolbox to open the Queue Viewer, or run the 'Get-Queue' and 'Get-Message' cmdlets in the Exchange Management Shell to view detailed error reasons for stuck messages.

Migration & Recovery