Commit Graph

10 Commits

Author SHA1 Message Date
547928426b Add my changes 2021-01-04 22:34:08 +01:00
Baptiste Jonglez
6d1d0ae4a8 Restart NSD when zone configuration has changed
This is necessary when a zone is added or removed: simply reloading NSD is
apparently not enough for it to take notice.
2017-09-01 21:42:24 +02:00
Baptiste Jonglez
cdf6821679 nsd: adapt for new version of NSD and allow to configure most parameters related to version (nsd3/nsd4) 2017-09-01 10:58:48 +02:00
Baptiste Jonglez
2ae5fd8b38 NSD: Validate configuration syntax using nsd-checkconf before applying 2017-09-01 10:20:48 +02:00
Baptiste Jonglez
93dd3810a0 NSD: Quote all paths 2017-09-01 10:20:48 +02:00
Baptiste Jonglez
6538ccda29 NSD: Reload database after having rebuilt it
Also don't restart nsd when changing zone configuration, rebuild + reload
is enough.
2017-09-01 10:20:48 +02:00
Baptiste Jonglez
eef721d276 NSD: Simplify configuration to use only one file for all zones, instead of many includes
This also allows the playbook to be idempotent.
2017-09-01 10:20:48 +02:00
Baptiste Jonglez
df14c7881f NSD: notify slaves when a primary zone is updated 2016-03-26 19:36:41 +01:00
Baptiste Jonglez
34f12ba81c NSD: Allow to configure the name of the TSIG keys
Of course, I forgot that the name of TSIG keys is relevant, since it needs
to be the same on both the master and the slave...

While we're at it, allow to define keys separately and refer them by name
in zone config, which avoids duplication.
2016-03-26 19:14:59 +01:00
Baptiste Jonglez
adc9f0b18e NSD: first playbook, still rough around the edges (no TSIG support) 2016-03-26 17:56:52 +01:00