dns problem - spamassassin bug?

[Alex Woick <al...@wombaz.de>]

I have two nameservers in my /etc/resolv.conf:

nameserver 10.10.10.11
nameserver 10.10.10.12

Now, the named daemon on 10.10.10.11 was stopped. The one on 10.10.10.12 
was still up. SpamAssassin, which is also running on 10.10.10.11, 
suddenly threw these errors upon every dns request:

Jun 26 19:49:36 lxrouter spampd[16461]: dns: sendto() failed: Connection 
refused at 
/usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/DnsResolver.pm line 
366, <_GEN_2> line 85.
Jun 26 19:49:36 lxrouter spampd[16461]: plugin: eval failed: oops, no 
key at /usr/lib/perl5/vendor_perl/5.8.8/Mail/SpamAssassin/AsyncLoop.pm 
line 120, <_GEN_2> line 85.

Isn't SpamAssassin supposed to try the next nameserver from resolv.conf 
on such a hard error? I expected that it would transparently fail over 
to 10.10.10.12 and use that server. Nothing else in my network 
encountered a problem with dns during the outtime, only Spamassassin.

(running SA 3.2.1 on Linux under Fedora 7)

Re: dns problem - spamassassin bug?

[Theo Van Dinter <fe...@apache.org>]

On Tue, Jun 26, 2007 at 08:26:22PM +0200, Alex Woick wrote:
> Isn't SpamAssassin supposed to try the next nameserver from resolv.conf 
> on such a hard error? I expected that it would transparently fail over 
> to 10.10.10.12 and use that server. Nothing else in my network 
> encountered a problem with dns during the outtime, only Spamassassin.

Net::DNS, which is what SA uses to call DNS, has been well known to only use
the first entry in resolv.conf, unfortunately.  fyi.

-- 
Randomly Selected Tagline:
Sarchasm: The gulf between the author of sarcastic wit, and the recipient
 who doesn't get it.
         - Washington Post