• RSS
  • Twitter
  • FaceBook

Exchange Server Forums

Forums | Register | Login | My Profile | Inbox | RSS RSS icon | My Subscription | My Forums | Address Book | Member List | Search | FAQ | Ticket List | Log Out

Unable to bind to the destination server in DNS.

Users viewing this topic: none

Logged in as: Guest
  Printable Version
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> Unable to bind to the destination server in DNS. Page: [1]
Login
Message << Older Topic   Newer Topic >>
Unable to bind to the destination server in DNS. - 8.Jul.2005 9:59:00 AM   
Jolo

 

Posts: 83
Joined: 6.Nov.2004
From: Brunei
Status: offline
I received this error on the Exchange System Manager ques, "Unable to bind to the destination server in DNS". What could be the reason for this? Im sending message between two exchange server with different domain. eg. user1@company.com and user2@company.biz. Any ideas?

I had created SMTP connectors between this two exchange mail servers but still doesn't work.

I need help please....
Post #: 1
RE: Unable to bind to the destination server in DNS. - 8.Jul.2005 12:40:00 PM   
Jolo

 

Posts: 83
Joined: 6.Nov.2004
From: Brunei
Status: offline
Surely its a Name resolution problem, what I did is to follow KB ID 823158.

Here are the steps..

1. Start Exchange System Manager, expand Recipients, and then click Recipient Policies.
2. Right-click Default Policy, and then click Properties.
3. Click the E-Mail Addresses tab.
4. In the Generation rules dialog box, click SMTP, and then click Edit.
5. At the bottom of the SMTP Address Properties dialog box, if the This Exchange Organization is responsible for all mail delivery to this address check box is selected, this Exchange organization is authoritative for that address space. If this check box is not selected, this Exchange organization is not authoritative for that address space.
When either Exchange 2000 Server or Exchange Server 2003 tries to deliver a message to a local address space (an address space that exists on a recipient policy), it tries to find the destination address in the Microsoft Active Directory directory service. If Exchange cannot find the destination address in Active Directory, the following occurs: If the Exchange organization is not authoritative, Exchange Server checks connectors and the Domain Name System (DNS) to find another route to that address space. If Exchange finds a connector with a matching address space, the message is routed to that connector. If Exchange does not find a connector, Exchange checks the DNS for a mail exchange (MX) record and routes the message to the corresponding host. If neither method is able to locate another route for the message, a non-delivery report (NDR) is generated with error code 5.4.0. This error code indicates that there is a name resolution issue.
If the Exchange organization is authoritative, Exchange Server immediately generates an NDR with error code 5.1.1. This error code indicates that the destination address does not exist. You can modify this behavior by specifying the fully qualified domain name (FQDN) or the IP address of the host where you want unresolved mail to be forwarded. To locate this setting, follow these steps:1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. If the Display administrative groups option is turned on, expand Administrative Groups, and then expand First Administrative Group (where First Administrative Group is the name of your administrative group).

Note To display administrative groups, right-click Your_Organization, click Properties, click to select the Display administrative groups check box, click OK two times, and then restart Exchange System Manager.
3. Expand Servers, expand Your_Exchange_Server, expand Protocols, and then expand SMTP.
4. Right-click SMTP virtual server, and then click Properties.
5. Click the Messages tab.
6. In the Forward all messages with unresolved recipients to host box, type either a FQDN or the IP address of the host that you want to forward all unresolved messages to authoritative domains.

Notes When you type the FQDN or the IP address, enclose it in square brackets ([]).
An NDR is not generated if messages are forwarded to this host. This setting does not affect domains where Exchange 2000 Server 2000 or Exchange Server 2003 is not authoritative.


Thanks God, I finally make it work after trial and errors on my setting for a week. [Roll Eyes] [Wink]

(in reply to Jolo)
Post #: 2

Page:   [1] << Older Topic    Newer Topic >>
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> Unable to bind to the destination server in DNS. Page: [1]
Jump to:

New Messages No New Messages
Hot Topic w/ New Messages Hot Topic w/o New Messages
Locked w/ New Messages Locked w/o New Messages
 Post New Thread
 Reply to Message
 Post New Poll
 Submit Vote
 Delete My Own Post
 Delete My Own Thread
 Rate Posts


Follow TechGenix on Twitter