Files
puppet-prod/site/profiles/manifests
unkinben 5b89e4336d
ci/woodpecker/pr/bolt-validate Pipeline was successful
ci/woodpecker/pr/erb-validate Pipeline was successful
ci/woodpecker/pr/epp-validate Pipeline was successful
ci/woodpecker/pr/yamllint Pipeline was successful
ci/woodpecker/pr/ruby-validate Pipeline was successful
ci/woodpecker/pr/puppet-lint Pipeline was successful
ci/woodpecker/pr/ruby-check Pipeline was successful
ci/woodpecker/pr/puppet-validate Pipeline was successful
dns: deploy dns-updater daemon in place of the shell nsupdate script
Replaces the profiles::dns::updater shell mechanism (dns-update.sh +
dns-update.path/.service + the in-run exec) with the packaged dns-updater
daemon, which watches the records file (inotify) and network interfaces and
pushes TSIG-signed RFC2136 updates natively.

- install the dns-updater package; manage /etc/dns-updater/env
- run the packaged dns-updater.service, restarting only on env/key change
  (records-file edits are picked up by the daemon's own watch, no churn)
- keep the concat records file and TSIG key file unchanged
- ensure the old script + .path/.service units are absent
- drop the now-dead dns-update.{sh,service,path}.epp templates

The daemon reports per-zone RCODEs and a health status API, so failures like
the recent empty-label/NOTZONE ones surface directly instead of as opaque
nsupdate stderr.
2026-07-17 23:20:05 +10:00
..
2024-04-13 22:34:28 +10:00
2025-07-06 11:27:35 +10:00
2023-11-17 22:17:24 +11:00
2025-06-29 13:36:16 +10:00
2026-01-03 21:51:47 +11:00
2024-06-01 22:51:42 +10:00
2024-07-01 22:54:22 +10:00
2025-06-15 17:43:19 +10:00
2024-03-16 16:43:12 +11:00
2024-07-08 22:33:11 +10:00
2026-03-16 23:53:52 +11:00
2023-11-17 22:25:43 +11:00
2024-08-06 22:33:32 +10:00
2025-04-24 16:51:31 +10:00
2025-04-24 23:03:01 +10:00
2024-07-28 01:51:41 +10:00