> On 12. 9. 2025, at 15:07, Nagesh Thati wrote:
>
> I am using --enable-singletrace option while compiling the BIND,
Why? What do you expect this does?
> will it cause any extra debug lines during query resolution, even if the rndc
> trace level is set to 0?
This is a debugging feature, so
Hi,
I am using *--enable-singletrace * 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?
Thanks
On Mon, Feb 10, 2025 at 1:02 PM Ondřej Surý wrote:
> I can't reproduce the issue.
>
> $ cat named.conf
> logging
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
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
7 matches
Mail list logo
