Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
+++ This bug was initially created as a clone of Bug #1680028 +++
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.
--- Additional comment from Henrique Martins on 2019-03-23 14:59:33 UTC ---
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.
--- Additional comment from Petr Menšík on 2019-09-11 11:02:31 UTC ---
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?
--- Additional comment from Henrique Martins on 2019-09-11 17:12:46 UTC ---
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.
--- Additional comment from Henrique Martins on 2019-09-12 11:56:05 UTC ---
Seems to be fixed in the current version.
Time to close this.
Thanks