Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

E2k3:Unable to bind to the destination server in dns


View products that this article applies to.

Symptoms

Source: Microsoft Support

RAPID PUBLISHING

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION IN RESPONSE TO EMERGING OR UNIQUE TOPICS, AND MAY BE UPDATED AS NEW INFORMATION BECOMES AVAILABLE.

↑ Back to the top


Cause

Customer is having two exchange organization,One is running on with a single exchange 2003 server , Domain name-domainone.com and the other one is running on with a single exchange 2003 server, Domain name-domaintwo.com.

He created a zone entry for domaintwo.com records in domainone.com Internal primary DNS server.He specified domaintwo.com DNS ip address under domainone.com Internal primary DNS server's forwarders list to have name resolution locally.

When he send an email from user@domainone.com to user@domaintwo.com,mails are getting queued up in the sending server with the error "Unable to bind to destination server in DNS"

↑ Back to the top


Resolution

In domainone.com Internal primary DNS server,under the domaintwo.com zone entry MX record for domaintwo.com's exchange server contains servername under "Host or Domain" section and it should be blank.

↑ Back to the top


More information

In domainone.com Internal primary DNS server,deleted MX record for domaintwo.com's exchange server and recreated the MX record by leaving "Host or Domain" section as blank and the record will default to "same as parent folder".

↑ Back to the top


Keywords: KB924251, kbrapidpub, kbtshoot, kbprb

↑ Back to the top

Article Info
Article ID : 924251
Revision : 3
Created on : 10/25/2007
Published on : 10/25/2007
Exists online : False
Views : 299