I have an issue where exchange fails to send mail. The queue fills up and when I check resolution for the remote host via nslookup (to my local DC) I get no IP address. If I restart the DNS service suddenly I am able to resolve the remote host. Any ideas on a correction for this other than restarting my dns server service every hour?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
DNS Resolution
- Thread starter MeenSeen
- Start date
WhoKilledKenny
MIS
Would you please post and error from your App, System, DNS, Security logs on the DC and Exchange servers.
Event ID : " " and description most helpful.
Event ID : " " and description most helpful.
- Thread starter
- #3
I get no errors on my DNS server. I do get this on my Exchange server:
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Connection Manager
Event ID: 4000
Date: 5/25/2007
Time: 9:18:52 AM
User: N/A
Computer: xxxxxxx
Description:
Message delivery to the remote domain 'anl.com.au' failed for the following reason: Unable to bind to the destination server in DNS.
Event Type: Warning
Event Source: MSExchangeTransport
Event Category: Connection Manager
Event ID: 4000
Date: 5/25/2007
Time: 9:18:52 AM
User: N/A
Computer: xxxxxxx
Description:
Message delivery to the remote domain 'anl.com.au' failed for the following reason: Unable to bind to the destination server in DNS.
WhoKilledKenny
MIS
I'm seeing a lot of articles on Google relating to your issue. Do a google search on - event id: 4000 unable to bind dns
Seems to be different issue depending on which version of OS and Exchange you are running.
Seems to be different issue depending on which version of OS and Exchange you are running.
- Status
Similar threads
- Locked
- Question