Forcing a secondary update...

[ivan jr sy]

maybe this will help
http://peppyheppy.com/2008/1/18/bulk-zone-file-serial-number-increment

--- On Tue, 1/27/09, Barry Margolin <barmar at alum.mit.edu> wrote:

> From: Barry Margolin <barmar at alum.mit.edu>
> Subject: Re: Forcing a secondary update...
> To: comp-protocols-dns-bind at isc.org
> Date: Tuesday, January 27, 2009, 2:12 PM
> In article <glleo1$2na5$1 at sf1.isc.org>,
>  Jeff Justice <listaccount at starionline.com> wrote:
> 
> > Without getting into how I managed to accomplish this,
> I have wound up  
> > with a secondary DNS that has incorrect information in
> it but the  
> > serial numbers are the same as on the master.
> > 
> > So, my question is:  how can I get the secondary to
> sync up?  I  
> > presume all I would need to do is make a single change
> to the zones on  
> > the master, thus changing the serial number, and
> causing the secondary  
> > to update.
> > 
> > The info in the master is correct, so I really
> don't need to change  
> > anything, but I could add something then delete it. 
> Is there an  
> > automated way I can do this, or batch method?  There
> are just enough  
> > zones as to make this a real hassle if I were to do it
> one by one.
> 
> You could delete the zone files on the slave server and
> then restart 
> named.  When it starts up and doesn't find zone files,
> it will have to 
> pull them from the master.
> 
> -- 
> Barry Margolin, barmar at alum.mit.edu
> Arlington, MA
> *** PLEASE don't copy me on replies, I'll read them
> in the group ***
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users