44net-request@hamradio.ucsd.edu wrote:

Subject: Re: [44net] Performance of DNS From: David Ranch amprgw@trinnet.net Date: 08/07/2014 03:04 AM

To: AMPRNet working group 44net@hamradio.ucsd.edu

Beyond filtering, are you looking at your named logs too? There are a ton of old / misconfigured DNS servers out there that don't support EDNS:

success resolving 'blns71.spamcop.net/A' (in 'spamcop.net'?) after disabling EDNS success resolving 'bcwww.enet.cu/A' (in 'enet.cu'?) after reducing the advertised EDNS UDP packet size to 512 octets

success resolving 'hispructs.com/A' (in 'hispructs.com'?) after reducing the advertised EDNS UDP packet size to 512 octets

I recognize that problem but it is not occurring on this server. Probably the ampr.org nameservers are not affected by that, and the machine does not make many other queries. The only recurring error messages are about IPv6 DNS server addresses being unreachable, but only one or two a day. I have now started it with -4 option but it will probably not change much. Also disabled dnssec. Let's see...

Rob