3 ms·
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
by tom_fitzhenry 14y ago
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 although my DNS is monitored, the monitoring isn't granular enough to detect sub-minute outages, for example.
Did you have any issues in particular with the stealth primary solution?
- zrail 14y agoNot any technical issues, it was just more moving pieces than I want. BuddyNS is a fine service but having to force an update with an email seemed pretty hacky.
- tom_fitzhenry 14y agoYou 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 https://tools.ietf.org/rfc/rfc1996.txt BIND 8+ supports it by default, according to http://docstore.mik.ua/orelly/networking_2ndEd/dns/ch10_03.htm http://docstore.mik.ua/orelly/networking_2ndEd/dns/ch10_03.h... There is a perl script to achieve the same thing in djbdns, according to http://www.fefe.de/djbdns/#notify http://www.fefe.de/djbdns/#notify (which joe_bleau alluded to).