FW: NOTIFY-triggered Auto-slaving
phn at icke-reklam.ipsec.nu
phn at icke-reklam.ipsec.nu
Fri Oct 4 12:37:23 UTC 2002
Paul Vixie <vixie at as.vix.com> wrote:
> "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".
To see this thread from another view: i do not think i would like
the idea that even inside an organization anyone could
create a zone and force MY nameservers to start slaving it.
We all know that dns servers are started by a lot of cluless folks
and the certenly don't always knows what they are doing.
Kevin, the functionality you need a a few perl-programs, one part run
at a central site ( when the domains and the master-slave relations
are designed ( not the word designed" ) and a few other programs
active at selected slave servers. I guess that there already are
implementations of this floating around.
--
Peter Håkanson
IPSec Sverige ( At Gothenburg Riverside )
Sorry about my e-mail address, but i'm trying to keep spam out,
remove "icke-reklam" if you feel for mailing me. Thanx.
More information about the bind-users
mailing list