Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the hueman domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /var/www/CloudIngenium.com/htdocs/wp-includes/functions.php on line 6114
Exchange Edge 2010: 451 4.4.0 DNS query failed – Knowledge eXchange

Exchange Edge 2010: 451 4.4.0 DNS query failed

What causes 451 4.4.0 DNS query failed on Exchange Server 2010?

After installing Microsoft Exchange Server 2010 Edge and subscribing to it all my emails were hanging on the queue and not being delivered to the hub server. I had all my network cards set up with my DNS server so I wash´t expecting any issues but I kept seeing the 451 4.4.0 DNS query failed message.

My first approach to solving this was to understand what DNS query was the one failing. While looking at the different settings I stumbled when I saw the smart host being “- -“. First I thought it was a typo and then I assumed the DNS was failing as it could not resolve that address. It turns out “- -” actually means the subscribed hub address so it automatically provides the correct hub address for you. Still confused as to what 451 4.4.0 DNS query failed meant so the next stop was the DNS resolution settings on the Exchange Edge server. If you go to the properties of your Exchange Edge server you’ll see a tab that reads “Internal DNS”. Here the default setting was to use the network card’s DNS automatically. I assumed that would work as the network card did have my internal DNS configured (which resolves outside addresses as well). It happens that for some reason that was not working.

The solution

Go into the properties of the Edge server and for the Internal DNS instead of using my network cards simply type in the address of the internal DNS and voila! That fixed it. For some reason is using not your internal DNS server (if you happen to have multiple set up) so it cannot resolve the hub transport address correctly. As simple as that.

For more information and troubleshooting steps if adding your internal DNS Server does´t work check out: Troubleshooting Mail Queues That Are Increasing on Edge Transport Servers

Enhanced by Zemanta

You may also like...

4 Responses

  1. Jason says:

    Thank you so much! Solved my problem 🙂

  2. Juan says:

    De mucha ayuda la informacion…
    Gracias totales

  3. KenSteve says:

    Works like a charm!

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.