"
I observed something similar with Kea/DDNS + BIND. In my case, the problem disappeared after changing these two DHCP settings:
`match-client-id: true`
`ddns-update-on-renew: false`
I then removed the affected `.jnl` files, let Kea create fresh leases/journals, and rebooted OPNsense. After the reboot, both the forward and reverse zones were still loaded and DNS worked normally.
Not sure if this is related, but maybe it helps someone else who runs into `journal rollforward failed: journal out of sync with zone`.
`match-client-id: true`
`ddns-update-on-renew: false`
I then removed the affected `.jnl` files, let Kea create fresh leases/journals, and rebooted OPNsense. After the reboot, both the forward and reverse zones were still loaded and DNS worked normally.
Not sure if this is related, but maybe it helps someone else who runs into `journal rollforward failed: journal out of sync with zone`.
