You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using this module to manage some zones in my bind9 installation. Additionally I setup bind to allow dynamic updates (for letsencrypt). However, this adds a new complexity level when changing a zone file. To prevent the zonefile to get out of sync with the journal file of dynamic updates, I would like to freeze a/all zone files before updating one (or more) zone files (with rndc freeze) and unfreeze them after the zone files have changed (with rndc thaw).
As you might see already, this has one main disadvantage: The freeze and thaw commands are executed at each puppet run, instead of only when the zone files get updated. This might not be a problem for the dynamic updates or the DNS server at all (exept from performance or maybe whatever), however it is unnecessary to execute these commands every half an hour (for the default time puppet runs).
So, this is a request to add a way in this module to freeze and unfreeze zones when they're updated.
The text was updated successfully, but these errors were encountered:
FlorianSW
added a commit
to droidwiki/operations-puppet
that referenced
this issue
Feb 23, 2019
By freezing before and unfreezing after a zone file update, the zone configuration
and the dynamic update journal does not get out of sync anymore.
However, one disadvantage of this solution is, that the (un)freeze commands are run
at every puppet run. See also thias/puppet-bind#99
I'm using this module to manage some zones in my bind9 installation. Additionally I setup bind to allow dynamic updates (for letsencrypt). However, this adds a new complexity level when changing a zone file. To prevent the zonefile to get out of sync with the journal file of dynamic updates, I would like to freeze a/all zone files before updating one (or more) zone files (with
rndc freeze
) and unfreeze them after the zone files have changed (withrndc thaw
).For now I implemented this like that:
As you might see already, this has one main disadvantage: The freeze and thaw commands are executed at each puppet run, instead of only when the zone files get updated. This might not be a problem for the dynamic updates or the DNS server at all (exept from performance or maybe whatever), however it is unnecessary to execute these commands every half an hour (for the default time puppet runs).
So, this is a request to add a way in this module to freeze and unfreeze zones when they're updated.
The text was updated successfully, but these errors were encountered: