rndc reconfig doesn't load new zones ???

[Lists User]

rndc reconfig "does" load the new configuration and all new zones.
It just doesn't do anything with zones that already existed.

rndc reload <zone> will reload the zone file if it has changed.



On Fri, 1 Feb 2002, Patrick Viola wrote:

> I thought, that rndc reconfig will load the new configuration AND all
> new zones.
> I wont do a rndc reload every time I add some zones ... This would
> reload 10thousand of zones :(
> 
> If there is no other posibility, I think I have to change my script to
> do a rndc reload <Zone> for every zone
> 
> Thanks anyway
> 
> ~Patrick
> 
> Lists User wrote:
> > 
> > Because I believe that is what rndc reload is for.
> > 
> > rndc reconfig was made to only add the new zones into bind
> > without the processing of all the zones again. Doesn't cause
> > named to down as long.
> > 
> > Why would you want to rndc reload and rndc reconfig to do
> > the exact same thing?  That would be a waste of development.
> > 
> > That doesn't make much sense.
> > 
> > On Thu, 31 Jan 2002, Patrick Viola wrote:
> > 
> > >
> > > Hi,
> > >  If I add new secondary zones to named.conf and do a rndc reconfig after
> > > that, bind will load it's new configuration, but NOT the zones!
> > >  I try rndc reload <Zone> ... the zone was loaded immediately.
> > >
> > >  Why does rndc reconfig NOT load new zones?
> > >  Anybody know this Prob and can tell me a solution?
> > >
> > > ~Patrick
>