bind 9 slave updating

[Barry Margolin]

In article <bnlgav$2msi$1 at sf1.isc.org>, David Hill <david at wmol.com> wrote:
>Hello -
>We setup a new nameserver running BIND 9.2.2.  The other nameservers
>including the master run 8.x.
>
>To add domains to each of the nameservers we run a script that puts it in
>named.conf on the master, adds it to a named.conf.export on the master which
>scp's the file over the other nameservers, then restarts the master.

Why do you restart the master?  "ndc reload" should be sufficient.

>The serial number does not change.

What serial number doesn't change?  If you're talking about new zones, they
didn't have an old serial number, so what would it mean to "change" them
if it's the first version?

>The 8.x slave servers change just fine (i guess cause the master tells them
>a domain has changed.  However, the bind 9.2.2 slave does not update.  If
>I -HUP the 9.2.2 slave, it properly loads the new config just fine.

No version of BIND I know of re-reads its named.conf unless you explicitly
tell it to.  You need to use "rndc reconfig" to make it learn about new
zones ("kill -HUP" went out with BIND 4, and has only been retained in
later versions for compatibility).

-- 
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.