[Bug 3626] New: is_dns_available failing consistently on certain hostnames

[bu...@bugzilla.spamassassin.org]

http://bugzilla.spamassassin.org/show_bug.cgi?id=3626

           Summary: is_dns_available failing consistently on certain
                    hostnames
           Product: Spamassassin
           Version: SVN Trunk (Latest Devel Version)
          Platform: Other
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P5
         Component: spamassassin
        AssignedTo: spamassassin-dev@incubator.apache.org
        ReportedBy: rOD-spamassassin@arsecandle.org


I've noticed that when I try restarting spamd, there's about a 50/50 chance that
DNS tests will fire.  Hunting around in my maillogs, I find that the
is_dns_available procedure bombs out with regularity on certain hostnames
(ebay.com, gmx.net and sourceforge.net, for example)

I have the latest Net::DNS installed, and am running bind locally.  nslookup and
dig work fine for these hosts.

Any thoughts?

[rod@blazing rod]$ sudo grep "NS lookup of" /var/log/maillog*
/var/log/maillog:Jul 21 00:42:43 blazing spamd[21303]: debug: NS lookup of
gmx.net failed horribly => Perhaps your resolv.conf isn't pointing at a valid
server?
/var/log/maillog:Jul 21 11:19:59 blazing spamd[10161]: debug: NS lookup of
ebay.com failed horribly => Perhaps your resolv.conf isn't pointing at a valid
server?
/var/log/maillog:Jul 21 14:49:03 blazing spamd[17319]: debug: NS lookup of
ebay.com failed horribly => Perhaps your resolv.conf isn't pointing at a valid
server?
/var/log/maillog:Jul 21 14:50:29 blazing spamd[17384]: debug: NS lookup of
mit.edu succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.1:Jul 11 19:56:22 blazing spamd[419]: debug: NS lookup of
w3.org succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.1:Jul 11 19:56:52 blazing spamd[507]: debug: NS lookup of
apache.org succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.1:Jul 11 23:10:57 blazing spamd[5551]: debug: NS lookup of
colorado.edu succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.1:Jul 15 21:40:16 blazing spamd[27934]: debug: NS lookup of
yahoo.com succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.1:Jul 15 21:42:36 blazing spamd[28042]: debug: NS lookup of
sourceforge.net failed horribly => Perhaps your resolv.conf isn't pointing at a
valid server?
/var/log/maillog.1:Jul 16 09:30:42 blazing spamd[17167]: debug: NS lookup of
linux.org succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.2:Jul  4 18:50:24 blazing spamd[25700]: debug: NS lookup of
google.com succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.2:Jul  4 23:01:56 blazing spamd[32432]: debug: NS lookup of
ebay.com failed horribly => Perhaps your resolv.conf isn't pointing at a valid
server?
/var/log/maillog.2:Jul  5 01:37:56 blazing spamd[9256]: debug: NS lookup of
google.com succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.2:Jul  5 17:03:39 blazing spamd[1504]: debug: NS lookup of
intel.com succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.2:Jul  5 17:10:44 blazing spamd[2659]: debug: NS lookup of
adelphia.net failed horribly => Perhaps your resolv.conf isn't pointing at a
valid server?
/var/log/maillog.2:Jul  5 17:11:32 blazing spamd[2737]: debug: NS lookup of
colorado.edu succeeded => Dns available (set dns_available to hardcode)
/var/log/maillog.2:Jul  5 20:51:18 blazing spamd[10146]: debug: NS lookup of
gmx.net failed horribly => Perhaps your resolv.conf isn't pointing at a valid
server?
/var/log/maillog.2:Jul  5 20:56:55 blazing spamd[10719]: debug: NS lookup of
apache.org succeeded => Dns available (set dns_available to hardcode)



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.