Matt Kettler wrote:
At 08:34 PM 9/26/2005, Rick Macdougall wrote:
Turns out it was the completewhois.com dns lookups failing with
input/output errors, timeouts, etc but a search on the tests page
didn't show any whois tests (I finally tracked them down with a
spamassassin -D and a grep through the /usr/local/share/spamassassin
rules),
Any reason that the completewhois.com dns tests are enabled by
default if the lookup almost never works ? (All my servers show
timeouts and input/output errors).
Really? looks to me like it works, but some of their servers are down.
From www.dnsstuff.com I tested it:
Searching for 94.141.39.208.combined-HIB.dnsiplists.completewhois.com
A record at m.root-servers.net [202.12.27.33]: Got referral to
J.GTLD-SERVERS.NET. [took 182 ms]
Searching for 94.141.39.208.combined-HIB.dnsiplists.completewhois.com
A record at J.GTLD-SERVERS.NET. [192.48.79.30]: Got referral to
dns3.elan.net. [took 198 ms]
Searching for 94.141.39.208.combined-HIB.dnsiplists.completewhois.com
A record at dns3.elan.net. [64.68.0.1]: Timed out. Trying again.
Searching for 94.141.39.208.combined-HIB.dnsiplists.completewhois.com
A record at dns1.completewhois.com. [216.151.192.222]: Reports that no
A records exist. [took 129 ms]
Looks to work, although the one server didn't answer, the next one did.
Interesting, on all of my servers I see Input/Output errors. Maybe
related to dnscache rather than using bind ? I'll run some internal
tests and see.
Rick
