Skip to content

451 4.4.0 DNS Query Failed: Fix the Exchange Queue Error

What the 451 4.4.0 DNS query failed error in Exchange means, how to tell a one-domain problem from an all-domain one, and how to clear the queue.

Nov 20, 2026 5 min read 1,242 words
451 4.4.0 DNS Query Failed: Fix the Exchange Queue Error
451 4.4.0 DNS query failed error in the Exchange queue
451 4.4.0 DNS query failed error in the Exchange queue

You open Queue Viewer on your Exchange server and see mail piling up. Each queue shows the same last error: "451 4.4.0 DNS query failed". Nothing bounces yet, but nothing leaves either.

This guide explains what the error means, how to tell which kind of DNS problem you have, and how to fix each one.

What 451 4.4.0 means#

The error has two parts. 451 is an SMTP reply for a temporary failure. It means "not now, try later". 4.4.0 is the enhanced status code. The middle 4 points to a network or routing problem. In RFC 3463, X.4.0 means "other or undefined network or routing status". Something went wrong, but the code itself doesn't say what.

The text "DNS query failed" fills in the gap. Your server tried to look up where to send the mail and got no usable answer. It could not find the MX record, or the IP behind it, for the domain you are writing to.

Note who reports it. This is your own server talking, not the remote one. The message has not reached the other side.

Is it a bounce?#

Not yet. A 451 is temporary, so Exchange keeps the message in the queue and tries again. If DNS starts working, the mail goes out on the next try.

If the problem lasts too long, the message expires and the sender gets a real bounce. Our guide to 550 5.4.316 message expired shows what that looks like.

So don't remove the contacts. The addresses are fine. The lookup is broken.

Two kinds of DNS failure#

Microsoft's guide to the 451 4.4.0 DNS query failed error splits it into two cases. Find yours first, because the fixes are not the same.

What you see Likely cause Where to fix it
Mail to one or a few domains is stuck The remote DNS servers ignore the AAAA query or send an odd reply A send connector for that domain
Mail to every outside domain is stuck The DNS server your Exchange server uses is not working Your own DNS, or external DNS on Exchange

To check, open Queue Viewer or run Get-Queue in the Exchange Management Shell. Look at how many queues show the error and which domains they are for.

How to fix 451 4.4.0 for one domain#

When only a few domains fail, the problem is often on their side. Some DNS servers don't answer the AAAA (IPv6) query the way Exchange expects. You can't fix their DNS, but you can route around it.

Step 1: Find the domain's mail server#

Look up the MX record for the stuck domain, and then the IP address of that host. Use the nslookup tool with the MX record type, or an online tool. Our guide to MX record lookup walks through it.

Step 2: Create a send connector for that domain#

Microsoft's workaround is a send connector just for the problem domain:

  1. In the address space, add the remote domain, such as contoso.com.
  2. In the network settings, choose "Route mail through the following smart hosts".
  3. Add the IP address of the MX host you found in step 1.
  4. Set smart host authentication to None.

Exchange now skips the DNS lookup for that domain and connects to the IP directly.

Step 3: Retry the queue and keep an eye on it#

Retry the queue and check that the mail drains. Note the IP you used. If the domain moves its mail server, your connector will point at the wrong place. So treat it as a stopgap and remove it once their DNS answers again.

How to fix 451 4.4.0 for all domains#

When every outside domain fails, the problem is on your side. By default, Exchange uses the DNS settings of its network adapter to route mail out. If that DNS server is down or can't reach the internet, every lookup fails.

Step 1: Test DNS from the Exchange server#

Run a lookup from the server itself, for example Resolve-DnsName gmail.com -Type MX in PowerShell. If it fails or times out, DNS is the problem, not Exchange.

Step 2: Fix your internal DNS#

Check that your internal DNS servers are running. Then make sure they can resolve outside names, either by root hints or by a forwarder to a public resolver. Clear the DNS cache on the DNS server and on the Exchange server after you change anything.

Step 3: Or point Exchange at external DNS#

Microsoft gives a second route. Open the properties of the Exchange server that hosts the send connector. Add the IPs of public DNS servers under External DNS Lookups. Then, on the send connector that routes mail to the internet, turn on "Use the external DNS lookup settings on servers with transport roles".

Step 4: Retry and test#

Retry the queues and send a test message to an outside address. A quick SMTP test confirms the remote server now answers.

How it compares to similar codes#

Code What it usually means Who fixes it
451 4.4.0 Your server's DNS lookup failed Your admin
4.4.7 The message waited too long in the queue Your admin
5.4.4 No route: the domain has no usable MX or A record Sender: check the address
554 5.4.14 Mail loop, hop count exceeded Admins on both sides

For the full list, see our guide to email bounce codes.

How to avoid it in outreach#

A bad domain in your list can look like a DNS error. If a domain has no MX record at all, every send to it fails and hurts your sender pattern.

  • Check domains before you send. A domain with no MX record can't receive mail.
  • Watch for typos. "gmial.com" fails a DNS lookup just like a broken server.
  • Verify addresses first. A verifier checks the domain and the mailbox in one pass.

DNS Query Failed Checklist#

  • Count how many domains show the error in Queue Viewer
  • For a few domains: find the MX host's IP and add a send connector
  • For all domains: test DNS from the Exchange server
  • Fix internal DNS or set external DNS lookups on Exchange
  • Clear DNS caches and retry the queues
  • Remove stopgap connectors once the remote DNS works

FAQ#

What does 451 4.4.0 DNS query failed mean?#

It means your mail server could not look up where to send a message. The DNS query for the domain's mail server got no usable answer, so the mail waits in the queue.

Will the stuck emails still be delivered?#

Usually, yes. Exchange keeps retrying. Once DNS works again, the queue drains. If it takes too long, the messages expire and bounce.

Why does it only happen with one domain?#

Most often that domain's DNS servers don't answer the AAAA query in the way Exchange expects. A send connector with a smart host is Microsoft's workaround.

Is this a problem with the recipient's address?#

No. The address may be fine. The lookup failed, so your server never reached their mail server.

Does Exchange Online show this error?#

The Microsoft guide covers Exchange Server 2010, 2013 and 2016 on your own hardware. The fixes above are for those servers.

Before your next campaign, make sure every address and domain is real. Check your list with the Tomba Email Verifier.

// start free

See who Tomba finds at any company

Type a company's domain to see its people, their roles and verified work emails, each with the pages it was found on. Free account, no card.

Free plan · No credit card required · GDPR & CCPA

Share
0 clapsEnjoyed it? Give a clap.
AU

// about the author

Tomba Editorial Team

Was this helpful?