23 Bře
2021
23 Bře
'21
8:21
Hi Libor,
On 22.03.21 16:40, libor.peltan wrote:
I was able to reproduce your issue and it occurs to be
a bug. We will
fix it for the next 3.0.x version.
Great, thank you.
You might use any of two possible workarounds:
1) after changing the configuration file by setting journal-content:
all, you can stop and cold-start knotd instead of reloading the
configuration.
2) before changing the configuration, you can stop the single affected
zone by `knotc -f purge +expire example.net.` and proceed with `knotc
reload`.
Both workarounds seem to work fine for our use case, thank you.
Regards
André