22 Čen
2018
22 Čen
'18
20:35
On 2018-06-22 19:56, Ondřej Caletka wrote:
Dne 21.6.2018 v 15:33 Daniel Salzman napsal(a):
Thank you for verification. However, we have discovered some minor
issues
with this use case. But I hope we will fix them in the next patch
release.
Daniel
This is an intended use case, so if it
doesn't work, it's a bug :-)
Definitely, you must set "zonefile-load: difference". Otherwise IXFR
changes would be incomplete.
Also I think you should set "journal-content: changes" to store just
changes to the journal.
The biggest problem is that you have to update the SOA serial to a
value higher than the current one
(not to the value higher than is in the zone file, which is not
managed by the server).
Hello Daniel,
thank you for response. I can confirm that using `journal-content:
changes` together with `zonefile-load: difference` works properly, that
means:
- when zone file is edited and SOA serial is set to be higher than
current serial of signed zone, the zone is resigned and this is
recorded
into the journal as a change (ie. there is still history in the
journal)
- when zone file is edited and SOA is not set to be higher than
current
serial of signed zone, only warning gets logged and nothing breaks.
So `journal-content: all` was the reason of all the strange behavior I
observed.
Cheers,
Ondřej Caletka