bind9

[Kevin Darcy]

those who know me have no need of my name wrote:

> <9vbivo$8mu at pub3.rc.vix.com> divulged:
> >In article <9vbhvg$8jq at pub3.rc.vix.com>, Jobe Bittman  <jobe at tns.net> wrote:
>
> >>I'm switching to bind9 and I'm interested in having my secondary name
> >>server automatically get names of zones to slave from the primary name
> >>server. Is that how NOTIFYs work? I thought this was what dynamic updates
> >>did, but now that I'm trying to set it up, I'm finding little information.
> >
> >There's nothing in the DNS protocol that allows you to get the list of
> >zones from a server.
>
> >The usual way to do what you want is to run a script that reads the
> >master's named.conf and changes all the "type master" clauses to "type
> >slave" and adds the "masters { <address of master>; }" clauses.  Then use
> >some kind of file transfer to move this to the slave.
>
> it's also possible to do this using dns as the data transfer mechanism.  it
> is, likewise, not automatic, and i wouldn't suggest it if you have very
> many zones.  use a special label that contains the names of all the zones
> you host and a view that prevents others from having visibility of that
> label.  and as with the solution barry presents, you write a script, that
> queries the special label using the result to construct the configuration
> file, finishing with an ``rndc reconfig''.
>
> while the dns protocol doesn't have anything to deal with this there's no
> particular reason that bind shouldn't consider such an addition, using a
> different (perhaps private) protocol that would support this notion, much
> as it does already for controlling the daemon.

DNMP = Domain Nameserver Management Protocol?


- Kevin