[Hampshire] named problem: FORMERR resolving...

Top Page

Reply to this message
Author: Chris Dennis
Date:  
To: Hampshire
CC: 
Subject: [Hampshire] named problem: FORMERR resolving...
Hello folks

My server's syslog is filling up with errors from named like this (sorry
about the wrapping)

-----
named[1874]: FORMERR resolving 'ns35.1und1.de/A/IN': 195.74.96.35#53
named[1874]: FORMERR resolving 'ns36.1und1.de/A/IN': 195.74.96.35#53
named[1874]: FORMERR resolving '34.200.201.193.sbl.spamhaus.org/TXT/IN':
195.74.96.34#53
named[1874]: FORMERR resolving 'ns35.1und1.de/A/IN': 195.74.96.20#53
named[1874]: FORMERR resolving 'ns36.1und1.de/A/IN': 195.74.96.20#53
named[1874]: unexpected RCODE (SERVFAIL) resolving
'190.173.56.69.sbl.spamhaus.org/TXT/IN': 195.74.96.173#53
named[1874]: FORMERR resolving '34.200.201.193.sbl.spamhaus.org/TXT/IN':
195.74.96.35#53
named[1874]: FORMERR resolving '45.159.47.78.sbl.spamhaus.org/TXT/IN':
195.74.96.34#53
named[1874]: unexpected RCODE (SERVFAIL) resolving 'ns35.1und1.de/A/IN':
195.74.96.173#53
named[1874]: unexpected RCODE (SERVFAIL) resolving 'ns36.1und1.de/A/IN':
195.74.96.173#53
named[1874]: unexpected RCODE (SERVFAIL) resolving
'34.200.201.193.sbl.spamhaus.org/TXT/IN': 195.74.96.173#53
named[1874]: unexpected RCODE (SERVFAIL) resolving
'45.159.47.78.sbl.spamhaus.org/TXT/IN': 195.74.96.173#53
named[1874]: FORMERR resolving '34.200.201.193.sbl.spamhaus.org/TXT/IN':
195.74.96.20#53
named[1874]: FORMERR resolving '45.159.47.78.sbl.spamhaus.org/TXT/IN':
195.74.96.35#53
named[1874]: FORMERR resolving '45.159.47.78.sbl.spamhaus.org/TXT/IN':
195.74.96.20#53
-----

DNS lookups are still basically working, although I have been noticing
occasional 'pauses' that might be caused by DNS timeouts.

These errors seem to happen for all sorts of lookups -- web pages or
mail servers etc. Some of the error lines have /AAAA/IN instead of
/A/IN, although I'm not using IPv6.

I'm not sure when it started happening -- I've been trying to solve it
for a few days, and my logs only go back 7 days.

The server is running up-to-date Debian Etch, with a 2.6.6 kernel.
Bind9 is at version 9.3.4-etch2, and hasn't been updated since
September; no newer updates are available.

/etc/default/bind9 contains: OPTIONS="-4 -u bind". Adding the -4 didn't
make any difference.

Much Googling etc. has failed to find a relevant answer.

Can anyone shed any light?

cheers

Chris
-- 
Chris Dennis                                  cgdennis@???
Fordingbridge, Hampshire, UK