You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2017/08/27 21:49:04 UTC
[Bug 7464] dbg: dns: query failed: 1.4.3.updates.spamassassin.org =>
SERVFAIL
https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7464
Bill Cole <sa...@billmail.scconsult.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sa-bugz-20080315@billmail.s
| |cconsult.com
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #1 from Bill Cole <sa...@billmail.scconsult.com> ---
(In reply to Toralf Förster from comment #0)
> Aug 26 16:03:16.251 [2003] dbg: dns: query failed:
> 1.4.3.updates.spamassassin.org => SERVFAIL
> Aug 26 16:03:16.256 [2003] dbg: dns: query failed:
> mirrors.updates.spamassassin.org => SERVFAIL
> channel: no 'mirrors.updates.spamassassin.org' record found, channel failed
> Aug 26 16:03:16.256 [2003] dbg: diag: updates complete, exiting with code 4
I cannot reproduce this.
I have tried sa-update and dig to test the TXT & SOA records for
mirrors.updates.spamassassin.org and 1.4.3.updates.spamassassin.org (which is
resolved via a CNAME pointing to 3.3.3. updates.spamassassin.org.) With dig I
tried all of these resolution paths: my own recursing resolver, Google and
Level3 public resolvers, and each of the authoritative nameservers for the
zone. All are providing identical correct answers and the same SOA serial
number for the zone.
SERVFAIL DNS responses can result from a wide range of different errors at any
point in the chain of nameservers between your local resolver and the
authoritative nameservers for the name being resolved. Having tested 8
resolution paths and finding no issues, the possibilities remaining are:
1. The issue was transient and has been resolved on its own.
2. The issue is specific to your particular DNS resolution path, and so in no
sense a bug in SpamAssassin.
For future reference, this sort of problem which is not likely to be within the
SpamAssassin code itself but instead most likely rooted in external services is
better addressed to the spamassassin-users mailing list, which has a much
larger audience of fellow sysadmins who may be able to corroborate the problem
and/or diagnose it.
--
You are receiving this mail because:
You are the assignee for the bug.