Red Hat Bugzilla – Bug 387191
logs flooded with EDNS messages.
Last modified: 2015-01-04 17:30:07 EST
so far this morning, I have 1792 messages like the following in my logs.. ov 16 10:59:36 firewall named[1642]: too many timeouts resolving 'clockmail.net/A' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:36 firewall named[1642]: too many timeouts resolving 'clockmail.net/MX' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:39 firewall named[1642]: too many timeouts resolving 'clockmail.net/A' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:39 firewall named[1642]: too many timeouts resolving 'clockmail.net/MX' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:39 firewall named[1642]: too many timeouts resolving 'rainwatch.cn/NS' (in 'rainwatch.cn'?): disabling EDNS Nov 16 10:59:43 firewall named[1642]: too many timeouts resolving 'clockmail.net/A' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:43 firewall named[1642]: too many timeouts resolving 'clockmail.net/MX' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:47 firewall named[1642]: too many timeouts resolving 'clockmail.net/A' (in 'clockmail.NET'?): disabling EDNS Nov 16 10:59:47 firewall named[1642]: too many timeouts resolving 'clockmail.net/MX' (in 'clockmail.NET'?): disabling EDNS Nov 16 11:15:20 firewall named[1642]: too many timeouts resolving 'wirejoin.cn/NS' (in 'wirejoin.cn'?): disabling EDNS Nov 16 11:30:55 firewall named[1642]: too many timeouts resolving 'ns2.affa-soft.com/A' (in 'affa-soft.com'?): disabling EDNS Nov 16 11:30:55 firewall named[1642]: too many timeouts resolving 'ns1.affa-soft.com/A' (in 'affa-soft.com'?): disabling EDNS How do I fix / disable this ? oddly, all the hostnames it complains about resolve just fine when run with 'host' from the command line.
Specify "edns no" option in options statement. But real problem is usually broken firewall or router which blocks big ( > 512b) packets. I recommend you try edns-udp-size 512; option and if your log also has many messages "..disabling EDNS" complete disable it.
*** This bug has been marked as a duplicate of 275091 ***