Dear Team,

I am currently using BIND 9.18.16 and have encountered an issue where debug
level 3, 5, and 99 logs are being recorded in the named.log, even though
the debug level is explicitly set to 0.

Could you confirm if there are any hardcoded logging configurations within
BIND that might cause these debug-level logs to be generated in specific
cases, regardless of the set debug level?

Here is the relevant configuration and output for your reference:

*Logging Definition in named.conf:*

logging {
    channel named {
        file "/var/named/log/named.log" versions 10 size 100M;
        severity dynamic;
        print-category yes;
        print-severity yes;
        print-time yes;
    };
    category default {
        named;
    };
};

*RNDC Status Output:*

# rndc status
version: ISC BIND 9.18.16
running on localhost: Linux x86_64 6.3.2-1.el7.elrepo.x86_64 #1 SMP
PREEMPT_DYNAMIC Tue May 9 13:46:08 EDT 2023
boot time: Mon, 27 Jan 2025 18:18:40 GMT
last configured: Tue, 28 Jan 2025 04:38:48 GMT
configuration file: /etc/named.conf (/opt/chroot/etc/named.conf)
CPUs found: 40
worker threads: 40
UDP listeners per interface: 40
number of zones: 2008 (0 automatic)  *debug level: 0*
xfers running: 0
xfers deferred: 0
soa queries in progress: 0
query logging is ON
recursive clients: 0/900/1000
tcp clients: 0/150
TCP high-water: 2
server is up and running

*Named Log Snippet:*

28-Jan-2025 05:08:33.003 client: *debug 3*: client @0x7fe7e8441f68
10.1.10.242#58980: UDP request
28-Jan-2025 05:08:33.003 client: *debug 5*: client @0x7fe7e8441f68
10.1.10.242#58980: using view '_default'
28-Jan-2025 05:08:33.004 security: debug 3: client @0x7fe7e8441f68
10.1.10.242#58980: request is not signed
28-Jan-2025 05:08:33.004 security: debug 3: client @0x7fe7e8441f68
10.1.10.242#58980: recursion available
28-Jan-2025 05:08:33.004 client: debug 3: query client=0x7fe7e8441f68
thread=0x7fe8427fc700(<unknown-query>): ns_query_start
28-Jan-2025 05:08:33.004 client: debug 3: query client=0x7fe7e8441f68
thread=0x7fe8427fc700(www.linkedin.com/A): qctx_init
28-Jan-2025 05:08:33.004 rate-limit: *debug 99*: client
@0x7fe7e8441f68 10.1.10.242#58980 (www.linkedin.com): rrl=(nil),
HAVECOOKIE=0, result=DNS_R_NXDOMAIN, fname=0x7fe7e852a380(1),
is_zone=1, RECURSIONOK=1, query.rpz_st=(nil)(0), RRL_CHECKED=0

I would appreciate it if you could help identify the cause of this behavior
and suggest any configuration changes or adjustments to suppress these
debug-level logs.

Thank you for your assistance.

Best regards,
Nagesh
-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from 
this list

ISC funds the development of this software with paid support subscriptions. 
Contact us at https://www.isc.org/contact/ for more information.


bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users

Reply via email to