bind918 malfunction?
Peter
pmc at citylink.dinoex.sub.org
Fri Sep 6 18:50:45 UTC 2024
On Fri, Sep 06, 2024 at 08:05:18PM +0200, Ondřej Surý wrote:
! Try using running `named -d 9 (plus other existing args)` to see why there are 31+ queries. There must be something wonky going on.
!
Alright. "-d 9" does nothing.
Changing the named.conf does something:
channel named_log {
syslog local0;
// severity info;
severity debug 99;
print-category yes;
print-severity yes;
};
channel activity_log {
syslog local1;
// severity info;
severity debug 99;
print-category yes;
print-severity yes;
};
category client { activity_log; };
category config { named_log; };
category database { named_log; };
category dnssec { activity_log; };
category general { named_log; };
category network { named_log; };
category notify { named_log; };
category queries { null; };
category query-errors { activity_log; };
category resolver { activity_log; };
category security { named_log; };
category update { named_log; };
category update-security { named_log; };
category xfer-in { named_log; };
category xfer-out { named_log; };
category unmatched { named_log; };
category default { named_log; };
Not sure if this is all we need. "queries" got me bored, as I
have dnstap anyway. If we need it, I must try to repeat - it
does not always happen. Here it did:
20:31:59# host ns4.edns.t-ipnet.de
Host ns4.edns.t-ipnet.de not found: 2(SERVFAIL)
Apparently the 99 is now a bit more than you wanted.
But - voila!
Sep 6 20:31:59 <local1.debug> pole named[71152]: resolver: debug 3: exceeded max queries resolving 'ns1.edns.t-ipnet.de/AAAA' (querycount=33, maxqueries=32)
cheerio,
PMc
More information about the bind-users
mailing list