When a user sends e-mail messages to a remote domain, some e-mail messages are queued on an Exchange Server Hub Transport server or Edge server

Article translations Article translations
Article ID: 972744 - View products that this article applies to.
Expand all | Collapse all

SYMPTOMS

You have a Windows Server 2008-based computer that is running Microsoft Exchange Server 2010 or Microsoft Exchange Server 2007. Additionally, you have the Hub Transport server role or the Edge server role installed. On this computer, you may find that e-mail messages that are sent to some remote domains are queued as "retryable." In addition, the Last Error on the queued items is shown "451 4.4.0 DNS query failed".

CAUSE

This problem occurs when the Exchange Server server tries to query AAAA records for the remote domain from a Domain Name System (DNS) server. However, either some DNS servers ignore the AAAA query or they return an unexpected response. This problem occurs because Exchange Server 2010 and Exchange Server 2007 do not use MX or A records.

Note The AAAA resource record type is a new record that is specific to the Internet class. Additionally, the AAAA resource is used to store a single IPv6 address.

WORKAROUND

To work around this issue, create Send connectors for the affected remote domains. Then, configure the Send connectors to use a smart host for remote MX records.

RESOLUTION

Exchange Server 2010

To resolve this problem in Exchange Server 2010, follow these steps:
  1. Modify the send connector to use External DNS.

    Set-SendConnector <connector name> -UseExternalDNSServersEnabled $true
  2. Ensure that DnsFaultTolerance is set to Lenient in the EdgeTransport.Exe.Config. For more information about this problem, visit the following Microsoft Web site: 

    General information about DNS Query Failure Sensitivity in Exchange 2007 SP1 and SP2
Exchange Server 2007

To resolve this problem in Exchange Server 2007, follow the following steps:
  1. Install the following update rollup:
    972076 Description of Update Rollup 2 for Exchange Server 2007 Service Pack 2
  2. Modify the send connector to use External DNS.
    Set-SendConnector <connector name> -UseExternalDNSServersEnabled $true
  3. Ensure that DnsFaultTolerance is set to Lenient in the EdgeTransport.Exe.Config. For more information about this problem, visit the following Microsoft Web site:
    General information about DNS Query Failure Sensitivity in Exchange 2007 SP1 and SP2

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 972744 - Last Review: April 13, 2012 - Revision: 3.0
APPLIES TO
  • Microsoft Exchange Server 2010 Enterprise
  • Microsoft Exchange Server 2010 Standard
  • Microsoft Exchange Server 2007 Service Pack 2, when used with:
    • Microsoft Exchange Server 2007 Standard Edition
    • Microsoft Exchange Server 2007 Enterprise Edition
Keywords: 
kbexpertiseinter kbfix kbhotfixrollup kbqfe kbsurveynew KB972744

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com