Simon Loewen writes:
Sam Varshavchik wrote:Simon Loewen writes:# dnsqr a dnsexit.com 1 dnsexit.com: 45 bytes, 1+1+0+0 records, response, noerror query: 1 dnsexit.com answer: dnsexit.com 600 A 67.214.175.75 # dnsmx dnsexit.com 1 mail.dnsexit.com 2 mail2.dnsexit.com Unforntunatly textmxlookup fails. # testmxlookup dnsexit.com Soft error.testmxlookup doesn't do just an A lookup, it does an MX lookup first, and then, depending on the response, may try additional A and/or AAAA lookups on the resulting hostnames. testmxlookup's far more sensitive to DNS hiccups than a single dig.Thanks Sam, but why cannot courier perform a DNS lookup? What sensibility does testmxlookup reveal? How can I mend this? - What is it likely that I missed?
Hard to say without looking into it yourself. If, for example, you are using your Internet provider's DNS servers, and only they have an internal problem, you're going to see issues that others won't.
Your best tool for analysis is to use the dig command, and not any other wrapper of any sorts. dig issues direct UDP DNS queries, much like testmxlookup. Use dig to try getting an MX record for your domain, then try A and AAAA records, and see if there are any failures. Also, try explicit queries against the zone's authoritative NSes. If one of them is down, that's one source of random DNS failures.
pgpmuzp3m9yf4.pgp
Description: PGP signature
------------------------------------------------------------------------------ Enter the BlackBerry Developer Challenge This is your chance to win up to $100,000 in prizes! For a limited time, vendors submitting new applications to BlackBerry App World(TM) will have the opportunity to enter the BlackBerry Developer Challenge. See full prize details at: http://p.sf.net/sfu/Challenge
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
