rndc reload on slave

[Barry Margolin]

In article <bleo5m$pc8$1 at sf1.isc.org>,
ALEXANDER RIEGER <ALEXANDER.RIEGER at dinits.de> wrote:
>Hi,
>
>i'm having the following problem:
>
>We have two dns servers with bind 4.9.7.  After changing an entry in
>one of the zone files we first reload the primary dns server with "ndc
>reload" and then the secondary dns server also with "ndc reload". The
>slave reload its configuration and all zone files.
>
>Now we have two new dns servers with bind 9.2.2. The servers running
>Red Hat Linux kernel 2.4.18-14. If we do the same as described above
>with "rndc reload" the slave reload it's configuration but no zone
>file
>is updated. Reloading only one zone with "rndc reload <zone>" works
>fine. I should have mention that we don't use dns notify.
>
>My question is if this is the expected behaviour with bind 9.2.2?

Yes.  BIND 4 refreshed every zone when it started or reloaded, which made
these operations take forever on servers with thousands of zones.  Since
BIND 8 they wait for the refresh interval to arrive.

Why don't you use notify?

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