Updating slaves servers?

Kevin Darcy kcd at daimlerchrysler.com
Wed Apr 4 21:07:16 UTC 2001


What do you mean by "a new record"? Are you talking about adding a resource
record, like an A record or an MX record? Those will get propagated to slaves, as
long as you increment the serial number on the zone. Or by "record" do you mean a
new zone definition? There is no standardized way to tell the slaves that they
should add a new zone definition. You'll have to write your own.


- Kevin

Jose Albert wrote:

> Well this part works well the changes on the main server records are
> updated to the slave, but what about adding a new record, how the slaves
> get aware of.
>
> Thanks
>
> -Jose
>
> jose at datacourse.com
> www.datacourse.com
>
> On Wed, 4 Apr 2001, Michael Kohne wrote:
>
> > At 11:50 AM 4/4/2001 -0700, Jose Albert wrote:
> > >Hi everybody
> > >
> > >Please can somebody tell me how to update slave servers.
> > >
> > >When a record is added to the main server this one then updates the slaves?
> > >
> > >I'm being updating the slave server manually.
> > >
> > >Any idea will be highly appreciated.
> > >
> > >Jose Albert
> >
> > If you update the serial number in the SOA for the zone you are updating,
> > then the slaves will automatically update. Either you will have to wait for
> > the refresh interval in the SOA to expire and the slaves to update, OR your
> > bind can send a NOTIFY to the slave servers, and if they are of an
> > appropriately recent version of bind, they will update automatically.
> >
> > Note that it is vital that you update the serial number: If you don't, then
> > the slaves will NOT update under any circumstances. Just increment the
> > serial number and the slaves should update next time they refresh, or when
> > they get the NOTIFY. (Of course, this assumes that the slaves are
> > configured in the usual manner.)
>





More information about the bind-users mailing list