I can't reproduce the issue.
$ cat named.conf
logging {
channel named {
file "named.log" versions 10 size 100M;
severity dynamic;
print-category yes;
print-severity yes;
print-time yes;
};
category default {
named;
};
};
I've run named and it is logging into the file:
$ wc -l named.log
882 named.log
$ tail named.log
10-Feb-2025 08:31:38.554 lame-servers: info: REFUSED unexpected RCODE resolving
'ns2.wirenet.com.ar/AAAA/IN': 190.52.32.3#53
10-Feb-2025 08:31:38.554 lame-servers: info: REFUSED unexpected RCODE resolving
'ns2.wirenet.com.ar/A/IN': 190.52.32.3#53
10-Feb-2025 08:31:38.558 lame-servers: info: REFUSED unexpected RCODE resolving
'ns1.wirenet.com.ar/AAAA/IN': 190.52.32.3#53
10-Feb-2025 08:31:38.886 lame-servers: info: success resolving
'a-0.19-a30f7000.c070081.1518.19d4.3ea1.410.0.tzin1lvkubqbfgzgrbj44qlek5.avqs.mcafee.com/A'
after disabling qname minimization due to 'ncache nxdomain'
10-Feb-2025 08:31:38.974 lame-servers: info: success resolving
'a.c-0.19-a309a081.c870082.1518.19d4.3ea1.210.0.gprbcpw39smc9azb9c4cbskdkq.avqs.mcafee.com/A'
after disabling qname minimization due to 'ncache nxdomain'
10-Feb-2025 08:31:39.014 resolver: info: shut down hung fetch while resolving
'mail.trak.spb.ru/A'
10-Feb-2025 08:31:39.274 lame-servers: info: SERVFAIL unexpected RCODE
resolving 'breath.net/A/IN': 202.31.186.53#53
10-Feb-2025 08:31:39.362 lame-servers: info: REFUSED unexpected RCODE resolving
'www.vinculame.com/A/IN': 208.91.198.79#53
10-Feb-2025 08:31:39.522 lame-servers: info: REFUSED unexpected RCODE resolving
'ad.yieldmanager.com/A/IN': 162.251.87.166#53
10-Feb-2025 08:31:39.626 lame-servers: info: REFUSED unexpected RCODE resolving
'kriss.re.kr/MX/IN': 134.75.30.1#53
but there are no debug lines:
$ grep debug named.log
Whatever you are doing, it looks like your local configuration / operations
problem.
Ondrej
--
Ondřej Surý (He/Him)
ond...@isc.org
My working hours and your working hours may be different. Please do not feel
obligated to reply outside your normal working hours.
> On 10. 2. 2025, at 6:37, Nagesh Thati <tcpnag...@gmail.com> wrote:
>
> Hello All,
> Any help on this is much appreciated.
> Thanks
> Nagesh.
>
> On Tue, Jan 28, 2025 at 11:27 AM Nagesh Thati <tcpnag...@gmail.com> wrote:
> Hi,
> Thank you for your prompt response.
> 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.
> Thanks,
> Nagesh
>
> On Tue, Jan 28, 2025 at 11:12 AM Ondřej Surý <ond...@isc.org> wrote:
> I wonder…. What do you think that
>
> severity dynamic;
>
> does in your configuration file and why you have it configured? Have you read
> the documentation on the logging in the ARM?
>
> 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.
>
> Ondrej
> --
> Ondřej Surý — ISC (He/Him)
>
> My working hours and your working hours may be different. Please do not feel
> obligated to reply outside your normal working hours.
>
> > On 28. 1. 2025, at 6:32, Nagesh Thati <tcpnag...@gmail.com> wrote:
> >
> > severity dynamic;
>
--
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
