resolver priming query complete
Josef Moellers
jmoellers at suse.de
Fri Jun 24 14:54:09 UTC 2022
Hi,
I'm trying to find out what causes named 9.16.20 to print this log
message "resolver priming query complete" in irregular intervals.
The problem had been reported some time ago
(https://gitlab.isc.org/isc-projects/bind9/-/issues/752) but should have
been fixed.
The named.conf file is pretty simple:
# /etc/named.conf
options {
stale-answer-enable no;
directory "/var/lib/named";
managed-keys-directory "/var/lib/named/dyn/";
dump-file "/var/log/named_dump.db";
statistics-file "/var/log/named.stats";
listen-on-v6 { any; };
notify no;
disable-empty-zone
"1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA";
geoip-directory none;
};
include "/etc/named.conf.include";
with nothing in /etc/named.conf.include
There is a /etc/named.d/views.conf file with these (partial) contents:
view "internal" {
:
forwarders {
10.1.99.100;
10.1.99.141;
};
};
view "external" {
:
zone "smam.sm" {
notify yes;
type master;
file "/var/lib/named/master/smam.sm.zone.ext";
allow-transfer { any; };
};
};
Can anybody please explain why/how this happens?
Thanks and have a nice weekend,
Josef
--
SUSE Software Solutions Germany GmbH
Frankenstraße 146
90461 Nürnberg
Germany
Geschäftsführer: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
(HRB 36809, AG Nürnberg)
www.suse.com
More information about the bind-users
mailing list