Hi Volker,

yes, I forgot this useful option. The freeze item in zone-status has four states: "no", "freezing" (= freeze in progress), "yes", "thawing". This is enough to safely check the status of freeze.

After the zone is freezed and zonefile flushed, you can get all the current records safely directly from the zonefile, including SOA. Anyway, you can still get all the records also by simply asking the server e.g. by kdig ;)

Hope everything's clear now.

Please let us know later your experience with zone freeze, so we could update the user manual as needed and handy.

BR,

Libor

Hi Libor,

thanks for your reply.

Am 06.09.2017 um 13:15 schrieb "libor.peltan@nic.cz" <libor.peltan@nic.cz>:

Hi Volker,

thank you for your question.

Your suggestion is almost correct, just a little correction:

knotc zone-freeze $ZONE
# wait for possibly still running events (check the logs manually or so...)

Would Daniels suggestion be enough, to check for another freeze? I want to have a shell command to edit the knot zone file without further checks needed, beside what the script does.

knotc zone-flush $ZONE # eventually with '-f' if zone synchronization is disabled in config

Okay I added -f to be sure

$EDITOR $ZONEFILE # you SHALL increase the SOA serial if any changes made in zonefile

Is there a safe way in this scenario to get the current SOA?

knotc zone-reload $ZONE
knotc zone-thaw $ZONE

Reload before thaw - because after thaw, some events may start processing, making the modified zonefile reload problematic.

I see. I wasn't sure about the order of these two commands, which has been one reason for me to just ask here on the list. :-)

Regards

   Volker

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