You can use DNS NOTIFY rather than sending an email. When the primary is updated, DNS NOTIFY will tell each secondary about the change. DNS NOTIFY is standardised in: https://tools.ietf.org/rfc/rfc1996.txt BIND 8+…
Though the stealth primary solution involves more moving pieces, and introduces zone transfers, which are more complex than provisioning via puppet, I've had no noticeable issues. I say "noticeable issues", because…
To further improve reliability, consider using a secondary-as-a-service (as well as your self-hosted secondary name service). This will only work if tinydns supports zone transfers (AXFR/IXFR), which as far as I can…
You can use DNS NOTIFY rather than sending an email. When the primary is updated, DNS NOTIFY will tell each secondary about the change. DNS NOTIFY is standardised in: https://tools.ietf.org/rfc/rfc1996.txt BIND 8+…
Though the stealth primary solution involves more moving pieces, and introduces zone transfers, which are more complex than provisioning via puppet, I've had no noticeable issues. I say "noticeable issues", because…
To further improve reliability, consider using a secondary-as-a-service (as well as your self-hosted secondary name service). This will only work if tinydns supports zone transfers (AXFR/IXFR), which as far as I can…