Microsoft KB Archive/884421

= Some of your SMTP e-mail messages may remain in your outgoing mail queues with a status of 'Unable to bind to the destination server in DNS' in Exchange 2000 Server and in Exchange Server 2003 =

Article ID: 884421

Article Last Modified on 10/25/2007

-

APPLIES TO


 * Microsoft Exchange Server 2003 Enterprise Edition
 * Microsoft Exchange Server 2003 Standard Edition
 * Microsoft Exchange 2000 Server Standard Edition

-





SYMPTOMS
In Microsoft Exchange 2000 Server and in Microsoft Exchange Server 2003, some of your SMTP e-mail messages may remain in your outgoing mail queues in Exchange System Manager. Additionally, if you view the properties of a message in Queue Viewer in Exchange 2000 Server, the Details tab shows the following status for the message:

Unable to bind to the destination server in DNS.

In Exchange Server 2003, the additional queue information shows the following status for the message:

SMTP could not connect to any DNS server

Additionally, you may see events that are similar to the following in the event log in Exchange 2000 Server: Event ID 4000

Source: SMTPSVC

Type: Warning

Description: Message delivery to the remote domain ' ' failed for the following reason: Unable to bind to the destination server in DNS.

In Exchange Server 2003, you may see events that are similar to the following event in the event log: Event ID 4000

Source: MSExchangeTransport

Type: Warning

Description: Message delivery to the remote domain ' ' failed for the following reason: SMTP could not connect to any DNS server.

These symptom may occur even if you add an SMTP connector and set it to forward e-mail messages to the address of a smart host.



CAUSE
This issue may occur if any one of the following conditions is true:
 * External Domain Name System (DNS) servers are configured incorrectly for the default SMTP virtual server in Exchange. You can view the configuration settings on the Delivery tab in the Advanced Delivery dialog box of the default SMTP virtual server.
 * The external DNS servers that are specified for the default SMTP virtual server are no longer available.
 * The Secure cache against pollution option in Microsoft Windows 2000 DNS is enabled. If the Secure cache against pollution option is enabled, it can prevent the DNS server from following up DNS referrals.

Important Do not disable the Secure cache against pollution option. Refer to the article in the &quot;Workaround&quot; section to deal with this issue.
 * The DNS servers are unavailable.
 * Networking issues (permanent or intermittent) are restricting access to the DNS servers.



WORKAROUND
To work around this issue, remove the external DNS server references in Exchange System Manager, and then restart Microsoft Internet Information Services (IIS).

To remove the external DNS server references, follow these steps:
 * 1) Start Exchange System Manager.
 * 2) If administrative groups are enabled, expand Administrative Groups, and then expand First Administrative Group.

If administrative groups are not enabled, go directly to step 3.
 * 1) Expand the Servers container, and then expand the   container.
 * 2) Expand the Protocols container, and then expand the SMTP container.
 * 3) Right-click Default SMTP Server, and then click Properties.
 * 4) Click the Delivery tab, and then click Advanced.
 * 5) Click Configure, and then click the first entry in the External DNS list.
 * 6) Click Remove.
 * 7) Remove each remaining entry from the External DNS list.
 * 8) Click OK three times.
 * 9) Quit Exchange System Manager.

To restart IIS, follow these steps:
 * 1) Open the Services snap-in.
 * 2) Right-click the IIS Admin Service, and then click Restart.
 * 3) In the Restart Other Services dialog box, click Yes to restart the dependency services.
 * 4) Close the Services snap-in.

If the symptoms still persist after you remove the external DNS server references in Exchange System Manager, check the Networking issues and perform the steps that are described in the following article to resolve this issue.

313264 DNS server referral chasing when the SecureResponses option is enabled

