Can not get a lick of debug information for a slew of queries that are coming back SERVFAIL

[Doug Freed]

On 4/22/25 3:27 AM, The Gorf wrote:
> bind version:BIND 9.18.33-1~deb12u2-Debian (Extended Support Version) <id:>
> 
> So it's pretty simple. Im getting a ton of SERVFAILs randomly and I can 
> neither figure out why nor figure out how to get bind to give me debug 
> information about why. The documentation here:
> https://kb.isc.org/docs/aa-01526 <https://kb.isc.org/docs/aa-01526>
> Hurts my head to read and references stuff that I can't figure out where 
> in the documentation it is to explain what it is.
> 
> I took the exact document on that page and switched everything to 
> "debug" and I have reset the server, rebooted the server, nothing. Here 
> is the exact one line bind produces in its logs for the query that is 
> generating the SERVFAIL:
> 
> 22-Apr-2025 01:08:17.138 queries: info: client @0x7ffa3cb78168 
> 192.168.8.104#47099 (ksc.wiki): query: ksc.wiki IN A + (10.30.160.20)
> 
> Nothing. And here is the query-errors file:
> geoff at NS1:/var/log/named$ cat query-errors | grep -i wiki
> geoff at NS1:/var/log/named$
> zilch.
> 
> So. what am I doing wrong here? Why can't I get any debug info out of this?
> 
> logging {
>       channel default_log {
>            file "/var/log/named/default" versions 3 size 20m;
>            print-time yes;
>            print-category yes;
>            print-severity yes;
>            severity debug;

"severity debug" is equivalent to "severity debug 1" and there's not 
much extra information written at the first debug level.  The KB article 
you linked uses "severity dynamic" which uses the server debug level to 
control what gets logged.  You've already set that to 99 based on 
replies elsewhere in the thread, so just fix the severity here and 
reload named, and you should get all the logs you need to figure out 
what's going on and then some.

-Doug