Created attachment 1537589 [details] named.conf Description of problem: Named seems to log named[XXXX]: resolver priming query complete for almost every name lookup, or so it seems. Version-Release number of selected component (if applicable): bind-9.11.5-2.P1.fc29.x86_64 How reproducible: Always Steps to Reproduce: 1. configure and run a local recursive caching resolver Actual results: Lots of root priming messages in the logs Expected results: Very few of those, if any Additional info: I run a recursive caching server, currently forward first to OpenDNS, and have these hints in named.conf: zone "." IN { type hint; file "named.ca"; }; Just compared the named.ca file to the output of a dig query for the root servers and they are the same (except for the comments in header/footer) What am I missing? Attaching my (sanitized) named.conf.
Explanation of this behaviour here: https://kb.isc.org/docs/aa-01537. Another ISC page: https://kb.isc.org/docs/aa-01309 claims: Fixed in 9.12.0, 9.11.3, 9.10.7 and 9.9.12, bug RT #45241 could cause named to send unnecessary and frequent priming queries. However, I now have bind-9.11.5-4.P4.fc29.x86_64 and I'm still getting lots of messages logged. Can be eliminated by querying all root servers for -tA and -tAAAA (or -tANY). I've added that to a 30m crontab for now.
Hi Henrique, sorry for great delay. This is strange issue, but I think I read something similar on release issue notes. Have you tried updated versions? Does this issue persist with more recent updates?
Yup, it's been a while. I'm now on: bind-9.11.10-1.fc30.x86_64 Disabled my root priming crontab job earlier today and the logs seem clean of that annoying message. I'll report back tomorrow and if still clean, it is time to close the bug.
Seems to be fixed in the current version. Time to close this. Thanks