#< #5.0.0 smtp; 5.4.7 - Delivery expired (message too old) 'DNS Soft Error looking up aol.com (MX) while asking recursive_nameserver1.parent. Error was: unable to reach nameserver on any valid IP' (delivery attempts: 0)> #SMTP#
Original message headers:
Received: from exch01.internal.edmondok.com ([192.168.xxx.xxx])by edmironport.edmondok.com with ESMTP; 29 Dec 2009 09:15:36 -0600 Received: from exch01.internal.edmondok.com ([192.168.xxx.xxx]) by edmironport.edmondok.com with ESMTP; 29 Dec 2009 09:15:40 -0600 Received: from EXCH01.internal.edmondok.com ([fe80::45fe:26d:54cd:6aeb]) by EXCH01.internal.edmondok.com ([fe80::xxxx:xxxx:xxxx:xxxx%10]) with mapi; Tue, 29 Dec 2009 09:15:19 -0600 From: Internal User <firstname.lastname@example.org> To: User <email@example.com> Date: Tue, 29 Dec 2009 09:15:18 -0600 Subject: Blood Drive Today Thread-Topic: Blood Drive Today Thread-Index: AcqImccN9I6lWOw9QuGSrMji25lA2A== Message-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx@EXCH01.internal.edmondok.com Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: multipart/alternative; boundary="_000_08B7F743EE3EF44F8B51C43EEB8902C4034FF1F5EXCH01interaled_" MIME-Version: 1.0 X-Auto-Response-Suppress: DR, OOF, AutoReply
Any ideas as to why this is occuring? I have the ironport appliance's (C150) DNS pointing to our internal DNS servers. I am able to resolve all mailservers to IPs via nslookup and can ping hotmail.com's servers, but not aol.com's or amtrak.com's (possibly by their design?). There are some MX issues with AOL and Amtrak, but not Hotmail. Any help is appreciated. Thanks,
Re: SMTP 5.4.7 - Delivery expired - unable to reach nameserver o
It looks like your DNS server(s) are overloaded or refusing their job for some other reason.
What is the response of your DNS servers when you request the problematic domains? Please try from Ironport nslookup and from any other nslookup/dig that is using the same DNS servers.
One thing that once bothered us was that our DNS servers where allowed to perform UDP queries only, some MX targets with a lot (in this case 18) of servers in their MX records exceeded the UDP packet size and DNS tried to switch over to TCP. that traffic was dropped so the DNS server never got it's result back. I think the MX records of AOL and Amtrak are not that bid (4 and 3 mail servers) but maybe it's a start.
You can also try to enable query logging on your DNS servers and check the results of that.
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...