Automatic Secondary NS

[Kevin Darcy]

I'm not sure why one would use TXT records for this. Use PTR records. They're not
restricted to reverse lookups, and, unlike TXT records, can benefit from
RDATA label compression. (I'm assuming that the only thing in the TXT records
would be the names of domains to slave; if there's other data in there, then
obviously TXT records would be a better solution).

Another approach would be to scrounge the would-be slave's logs for new
NOTIFY messages.

For very limited internal-root namespaces, it is possible for a script on each
slave to walk the namespace tree (with appropriate "branch pruning" logic, if
necessary) to determine what zones should be slaved or not. I have a
privately-developed script which does this on all of my internal slaves.


- Kevin

Michael Kjorling wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I recall that someone here had written a script that used a special
> zone with TXT records to keep track of the zones, and simply
> regenerate named.conf from that zone and reloading.
>
> An option? Search the archives for TXT and zones (not zone).
>
> Michael Kjörling
>
> On Jun 5 2001 12:48 -0400, 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.
> >
> > Todd.
>
> - --
> Michael Kjörling - michael at kjorling.com - PGP: 8A70E33E
> "We must be the change we wish to see" (Mahatma Gandhi)
>
> ^..^     Support the wolves in Norway -- go to     ^..^
>  \/   http://home.no.net/ulvelist/protest_int.htm   \/
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.6 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iD8DBQE7HRPXKqN7/Ypw4z4RApTdAKDGmU20+mJ5TaWe5uMHp32zpFBLjgCfbg8G
> leQ6HUMmq8qgArDy5uXOq60=
> =KvWo
> -----END PGP SIGNATURE-----