<div dir="ltr">Hi,<br>I am using
<strong>--enable-singletrace </strong> option while compiling the BIND, will it cause any extra debug lines during query resolution, even if the rndc trace level is set to 0?<br>Thanks</div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Mon, Feb 10, 2025 at 1:02 PM Ondřej Surý <<a href="mailto:ondrej@isc.org">ondrej@isc.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I can't reproduce the issue.<br>
<br>
$ cat named.conf<br>
logging {<br>
channel named {<br>
file "named.log" versions 10 size 100M;<br>
severity dynamic;<br>
print-category yes;<br>
print-severity yes;<br>
print-time yes;<br>
};<br>
category default {<br>
named;<br>
};<br>
};<br>
<br>
I've run named and it is logging into the file:<br>
<br>
$ wc -l named.log<br>
882 named.log<br>
<br>
$ tail named.log<br>
10-Feb-2025 08:31:38.554 lame-servers: info: REFUSED unexpected RCODE resolving '<a href="http://ns2.wirenet.com.ar/AAAA/IN" rel="noreferrer" target="_blank">ns2.wirenet.com.ar/AAAA/IN</a>': 190.52.32.3#53<br>
10-Feb-2025 08:31:38.554 lame-servers: info: REFUSED unexpected RCODE resolving '<a href="http://ns2.wirenet.com.ar/A/IN" rel="noreferrer" target="_blank">ns2.wirenet.com.ar/A/IN</a>': 190.52.32.3#53<br>
10-Feb-2025 08:31:38.558 lame-servers: info: REFUSED unexpected RCODE resolving '<a href="http://ns1.wirenet.com.ar/AAAA/IN" rel="noreferrer" target="_blank">ns1.wirenet.com.ar/AAAA/IN</a>': 190.52.32.3#53<br>
10-Feb-2025 08:31:38.886 lame-servers: info: success resolving '<a href="http://a-0.19-a30f7000.c070081.1518.19d4.3ea1.410.0.tzin1lvkubqbfgzgrbj44qlek5.avqs.mcafee.com/A" rel="noreferrer" target="_blank">a-0.19-a30f7000.c070081.1518.19d4.3ea1.410.0.tzin1lvkubqbfgzgrbj44qlek5.avqs.mcafee.com/A</a>' after disabling qname minimization due to 'ncache nxdomain'<br>
10-Feb-2025 08:31:38.974 lame-servers: info: success resolving '<a href="http://a.c-0.19-a309a081.c870082.1518.19d4.3ea1.210.0.gprbcpw39smc9azb9c4cbskdkq.avqs.mcafee.com/A" rel="noreferrer" target="_blank">a.c-0.19-a309a081.c870082.1518.19d4.3ea1.210.0.gprbcpw39smc9azb9c4cbskdkq.avqs.mcafee.com/A</a>' after disabling qname minimization due to 'ncache nxdomain'<br>
10-Feb-2025 08:31:39.014 resolver: info: shut down hung fetch while resolving '<a href="http://mail.trak.spb.ru/A" rel="noreferrer" target="_blank">mail.trak.spb.ru/A</a>'<br>
10-Feb-2025 08:31:39.274 lame-servers: info: SERVFAIL unexpected RCODE resolving '<a href="http://breath.net/A/IN" rel="noreferrer" target="_blank">breath.net/A/IN</a>': 202.31.186.53#53<br>
10-Feb-2025 08:31:39.362 lame-servers: info: REFUSED unexpected RCODE resolving '<a href="http://www.vinculame.com/A/IN" rel="noreferrer" target="_blank">www.vinculame.com/A/IN</a>': 208.91.198.79#53<br>
10-Feb-2025 08:31:39.522 lame-servers: info: REFUSED unexpected RCODE resolving '<a href="http://ad.yieldmanager.com/A/IN" rel="noreferrer" target="_blank">ad.yieldmanager.com/A/IN</a>': 162.251.87.166#53<br>
10-Feb-2025 08:31:39.626 lame-servers: info: REFUSED unexpected RCODE resolving '<a href="http://kriss.re.kr/MX/IN" rel="noreferrer" target="_blank">kriss.re.kr/MX/IN</a>': 134.75.30.1#53<br>
<br>
but there are no debug lines:<br>
<br>
$ grep debug named.log<br>
<br>
Whatever you are doing, it looks like your local configuration / operations problem.<br>
<br>
Ondrej<br>
--<br>
Ondřej Surý (He/Him)<br>
<a href="mailto:ondrej@isc.org" target="_blank">ondrej@isc.org</a><br>
<br>
My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.<br>
<br>
> On 10. 2. 2025, at 6:37, Nagesh Thati <<a href="mailto:tcpnagesh@gmail.com" target="_blank">tcpnagesh@gmail.com</a>> wrote:<br>
> <br>
> Hello All,<br>
> Any help on this is much appreciated.<br>
> Thanks<br>
> Nagesh.<br>
> <br>
> On Tue, Jan 28, 2025 at 11:27 AM Nagesh Thati <<a href="mailto:tcpnagesh@gmail.com" target="_blank">tcpnagesh@gmail.com</a>> wrote:<br>
> Hi,<br>
> Thank you for your prompt response.<br>
> I configured the logging severity as dynamic to allow me to change the severity level at any time using the rndc command. I have also reviewed the release notes for all versions released after BIND 9.18.16, but I did not find any bug fixes related to debug logging in any of those releases.<br>
> Thanks,<br>
> Nagesh<br>
> <br>
> On Tue, Jan 28, 2025 at 11:12 AM Ondřej Surý <<a href="mailto:ondrej@isc.org" target="_blank">ondrej@isc.org</a>> wrote:<br>
> I wonder…. What do you think that<br>
> <br>
> severity dynamic;<br>
> <br>
> does in your configuration file and why you have it configured? Have you read the documentation on the logging in the ARM?<br>
> <br>
> Also - don’t run old versions of BIND 9, you are almost 20 versions behind the latest 9.18 release, that’s year an half of bug fixes and security issues remedies.<br>
> <br>
> Ondrej<br>
> --<br>
> Ondřej Surý — ISC (He/Him)<br>
> <br>
> My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.<br>
> <br>
> > On 28. 1. 2025, at 6:32, Nagesh Thati <<a href="mailto:tcpnagesh@gmail.com" target="_blank">tcpnagesh@gmail.com</a>> wrote:<br>
> > <br>
> > severity dynamic;<br>
> <br>
<br>
</blockquote></div>