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 nam
Hello All,
Any help on this is much appreciated.
Thanks
Nagesh.
On Tue, Jan 28, 2025 at 11:27 AM Nagesh Thati 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 hav
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
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
4 matches
Mail list logo
