|
From: Kris D. <kd...@vi...> - 2006-12-11 15:51:13
|
Jamie Cameron wrote: > You need to click the Apply Changes button at the bottom of the main > page in the BIND module after adding zone. In a cluster setup, this will > restart both the master and slave servers, and so should trigger the > transfer of both forward and reverse zones.. Curious... if a zone is updated (and the serial incremented <g>), and the master is reloaded, it *should* send a NOTIFY to the slave server(s), which will then AXFR the zone. Logfiles from both sides would be interesting to see for the failure case. I have a local RBL passed on to several local slaves this way; the zone file is regenerated and BIND (master) reloaded about every twenty minutes. The only case I can think of where this might not happen is if NOTIFY has been disabled - in an all-BIND DNS environment, I can't see any advantage to doing so. This obviously doesn't apply to *adding* or *removing* zones; so far as I know there's no way to do that automatically through BIND's own internal processing. :/ -kgd |