managed-keys-error since BIND-9.16.15

[Tom]

I see the same error also on a couple of slave zones on a updated 
authoritative server, not only on the "managed-keys.bind"-file. So this 
is also not critical and can be ignored?

03-May-2021 00:20:28.532 general: error: 
/var/named/slave/example.com.hosts.jnw: journal file corrupt: expected 
serial 2021050100, got 2021050300
03-May-2021 00:20:28.532 general: error: zone example.com/IN: 
dns_journal_compact failed: unexpected error

Thank you.
Kind regards,
Tom


On 01.05.21 08:52, Mark Andrews wrote:
> Named should automatically correct this error. The journal version was not updated when the transaction header was updated. This has been corrected and named detects the unexpected transaction header and writes out a corrected journal.
>