bind9 incorrectly logs "starting maxtime timer" debug messages as errors

[Ondřej Hošek]

bind9 version 1:9.18.1-1ubuntu1.3, when performing zone transfers, incorrectly logs a debug message ("starting maxtime timer") with an ERROR log level.

Example of such a message:

Fri Mar 17 08:21:02 CET 2023 : named error: client @0x7f001ddc4e18 192.0.2.146#34331 (17.172.in-addr.arpa): transfer of '17.172.in-addr.arpa/IN': starting maxtime timer 7200000 ms

This has been acknowledged upstream: https://gitlab.isc.org/isc-projects/bind9/-/issues/3208

I kindly request that the fix be pulled into Ubuntu 22.04 LTS (jammy). Thanks in advance!

[Sergio Durigan Junior (sergiodj)]

Thanks for taking the time to report this bug.

We're currently working on updating the bind9 version that's shipped in Ubuntu Jammy, and this bug will be fixed by this update. I am subscribing the person responsible for this effort so that she's aware of the bug and can close when the new bind9 reaches jammy-updates. Thanks.

[Lena Voytek (lvoytek)]

9.18.12 has been released to Jammy now so this should be fixed. If you still experience this issue please let me know.

Thanks