Hi Georg,

On 12/08/2016 12:36 PM, georg@riseup.net wrote:
Hi Daniel.

Sorry, I've overlooked your mail.. :(
No problem :-)
On 16-12-01 14:45:07, Daniel Salzman wrote:
Yesterday, we have fixed the double free. But this issue still
requires some testing, because automatic signing with disabled zone
file synchronization brings some problems.
Sounds great, thanks for that!

How do you update the zone file and what type of changes do you do?
Do you simply reload the server or restart?
If setting up a machine with knot I'm using puppet to do the install and
to provide "base files" containing essential information like SOA etc.
for the configured zones. After this, I'm using DDNS updates exclusively
to add and delete records, nothing fancy. Sounds quite safe, doesn't it?
Yes, your use case is quite safe. The only thing that you have to
ensure is the maximum journal size. Because the changes are cumulating.
In the upcoming 2.4 release, the new zone journal will be able
to merge the oldest changes to reduce the journal occupation.

Best,
Daniel
Thanks for your work,
all the best,
Georg


_______________________________________________
knot-dns-users mailing list
knot-dns-users@lists.nic.cz
https://lists.nic.cz/cgi-bin/mailman/listinfo/knot-dns-users