Newbie question on lots of slave zones

[Barry Margolin]

In article <bn959q$1e7b$1 at sf1.isc.org>,
David E. Smith <dave at technopagan.org> wrote:
>I don't think there's a quick easy way to do this, but I can hope ...
>
>I want to set up one DNS server (ns1.foo.com) that will be doing primary 
>DNS for about 600 zones, plus acting as a caching server for a few 
>thousand dialup customers. The caching thing is easy...
>
>What I'd like to do is set up ns1.foo.com so that any changes made to it 
>are automatically propagated to ns2.foo.com. Change a zone file? It 
>propagates. Create a new zone, or cease to be authoritative for a zone? It 
>propagates. Et cetera.
>
>I know this can be done by putting a whole lot of slave directives on ns2, 
>and telling it that ns1 is the master, but that doesn't cover the 'I got a 
>new zone' part of the problem.

BIND contains nothing to automate this part.  Many sites write a script
that reads the master's named.conf file and changes all the "type master"
to "type slave" statements and adds "master {<ip>}", then scp's the
resulting file over to the slaves.

-- 
Barry Margolin, barry.margolin at level3.com
Level(3), Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.