Tried that.  The Ping resolves to the IP with no problem.  Every conventional testing tool reports the IP of the mailserver, which is why I'm having trouble narrowing it down.  About the only thing I haven't tried is rebooting the server.
 
Thanks
Robb


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Del Hines
Sent: Monday, November 17, 2003 12:47 PM
To: [EMAIL PROTECTED]
Subject: [Modus] Weird NDR?

The DNS cache on the mail server may be corrupt.  You can sometimes test this by doing a ping instead of a nslookup. If this is the problem, an “ipconfig /flushdns” should correct it.

 

- Del

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robb Bryn
Sent: Monday, November 17, 2003 11:07 AM
To: [EMAIL PROTECTED]
Subject: [Modus] Weird NDR?

 

I'm getting an NDR for the following address - [EMAIL PROTECTED]   The server reports a DNS failure but it resolves just fine from NSLookup (even tried from the server itself).  I am able to telnet to the destination mail server (tlcfl.com.mail5.psmtp.com:25) with no problem.  Where else can I look? We're on Modus 3... Error reports below....

 

Thanks

Robb

 

 

 

Your message has encountered delivery problems to the following recipient(s):

[EMAIL PROTECTED]

(Was addressed to [EMAIL PROTECTED])

Delivery failed

Unable to deliver to destination domain

Cannot resolve

 

Reporting-MTA: dns; MAKO.capefearcomputercenter.com
Received-From-MTA: dns; barracuda (unverified [63.151.254.178])
Arrival-Date: Mon, 17 Nov 2003 11:54:01 -0500

Final-Recipient: rfc822; [EMAIL PROTECTED]
Action: failed
Status: 5.4.4 (Permanent failure - routing/network: unable to route)

Reply via email to