Automatic Secondary NS

[Danny Mayer]

Todd Snyder wrote:

> in that case, are there any tools that will make the changes?
>
> Once I finish my current project, I'm going to start writing something (been
> on my todo list for a while) .. but if theres something out there, or if
> someone has a script they've already written...
>
> I plan on using expect a bunch, unless someone else can beat me over the
> head with something else (please!  I hate expect).
>
> It's a fairly obvious kind of thing - working at an ISP, whenever add a
> domain, we have to update the secondary.  It would be much nicer if there
> was one tool that would update both for provisioning.

    Actually it's not.  You are making a fundamental error in thinking that a
slave
needs to serve all zones that the master of any one zone serves.  That's not
true.  You can mix and match any number of slaves and masters in any way
you feel like it.  For example, if you have two nameservers and 4 zones to
serve, you could set up two of the zones to be mastered on  server A and slaved
on server B and the other two zones to be mastered on server B and slaved
on server A.  If you have 3 namservers and 21 zones you could distribute the
mastering to have 7 zones master on  each nameserver and slaved on the other
two.

    How you decide to do this is an administrative decision not a nameserver
decision.

        Danny