About 45 minutes after upgrading bind9 and logcheck I started getting messages like these: Feb 14 10:28:55 corn named[24777]: too many timeouts resolving 'safebrowsing.clients.google.com/A' (in 'com'?): reducing the advertised EDNS UDP packet size to 512 octets Feb 14 10:28:55 corn named[24777]: too many timeouts resolving '36.106.70.75.in-addr.arpa/PTR' (in '75.in-addr.arpa'?): reducing the advertised EDNS UDP packet size to 512 octets Feb 14 10:43:10 corn named[24777]: network unreachable resolving '3.55.255.193.in-addr.arpa/PTR/IN': 2001:503:ba3e::2:30#53 (Is the thing at the end of the previous line an IPv6 address?).
At least some of the addresses involved look legit: Feb 14 15:02:17 corn named[3637]: too many timeouts resolving 'mozilla.com/NS' (in 'mozilla.com'?): reducing the advertised EDNS UDP packet size to 512 octets Feb 14 15:02:20 corn named[3637]: network unreachable resolving 'ns1.mozilla.org/A/IN': 2001:500:e::1#53 Before the upgrade, the logs had a lot of these: Feb 11 08:35:14 corn named[23816]: too many timeouts resolving '141.110.53.159.zen.spamhaus.org/A' (in 'zen.spamhaus.org'?): disabling EDNS though logcheck did not report them. Does anyone know what's going on? Do the messages indicate any real problems with my nameserver or networking setup? Or has bind simply changed its routine messages, and logcheck patterns are not keeping up? I was already running lenny when this happened. Thanks. Ross -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
