>> 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. > >
DNS on the server works well as verified with dig and getent, yet testmxlookup fails with Soft Error. My original question remains unanswered: How does courier consult DNS? Dianostics below: *** getent works ; return codes included for fun! # echo $? 0 # getent dnstest.com getent: unknown database: dnstest.com # echo $? 1 # getent hosts dnstest.com 208.67.9.238 dnstest.com # echo $? 0 *** Dig works well # dig ; <<>> DiG 9.4.2-P2 <<>> ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 23977 ;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 518400 IN NS a.root-servers.net. . 518400 IN NS b.root-servers.net. . 518400 IN NS c.root-servers.net. . 518400 IN NS d.root-servers.net. . 518400 IN NS e.root-servers.net. . 518400 IN NS f.root-servers.net. . 518400 IN NS g.root-servers.net. . 518400 IN NS h.root-servers.net. . 518400 IN NS i.root-servers.net. . 518400 IN NS j.root-servers.net. . 518400 IN NS k.root-servers.net. . 518400 IN NS l.root-servers.net. . 518400 IN NS m.root-servers.net. ;; Query time: 446 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Fri Jul 10 01:04:28 2009 ;; MSG SIZE rcvd: 228 # dig dnstext.com ; <<>> DiG 9.4.2-P2 <<>> dnstext.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 47908 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dnstext.com. IN A ;; Query time: 337 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Fri Jul 10 01:04:40 2009 ;; MSG SIZE rcvd: 29 # dig mx dnstext.com ; <<>> DiG 9.4.2-P2 <<>> mx dnstext.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 36511 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;dnstext.com. IN MX ;; Query time: 115 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Fri Jul 10 01:04:55 2009 ;; MSG SIZE rcvd: 29 *** testmxlookup # echo $? 0 # testmxlookup dnstest.com Soft error. # echo $? 0 --> testmxlookup thinks it did its job well, but did not. Inside djbdns I have the entries for both 127.0.0.1 and the IP 192.168.1.200 (inside /etc/dnscache/env/IP) Bit confused, me. ------------------------------------------------------------------------------ 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
