FW: NOTIFY-triggered Auto-slaving

Paul Vixie vixie at as.vix.com
Fri Oct 4 01:35:00 UTC 2002


"David Botham" <dns at botham.net> writes:

> Primary Master sends "ASLAVE" packet to the slave(s).  Here is the
> packet breakdown:

i think there's an easier way.  put the list of zones to be slaved
into a metazone, and fetch that.  run a cron job to generate a named.conf
"include" file from this slave file.  whenever it changes, do "[r]ndc reload".

that way there's no explicit transaction needed to delete a slave zone; you
just remove its name from the metazone.

the only thing really needed in bind to support this is zone triggers so
that you don't need the cron job.

zone "zones-from-phred.phred.com" {
        type slave;
        masters { 192.168.0.1; };
        trigger new-zone exec "/var/named/new-zone.sh $";
};

where "$" is replaced by the zone name, and this is also allowed in "option".


More information about the bind-users mailing list