Forcing a secondary update...

[Matthew Pounsett]

On 26-Jan-2009, at 17:50, Jeff Justice 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.

An update to the serial number is the indicator to the master, and  
then to the slaves, that some change has occurred and the zone should  
be re-loaded or transferred.. but an actual change to the data isn't  
required to make that happen.  You can just update the serial number  
on the master and tell it to reload without altering any other data...  
the rest will take care of itself.

Matt



-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20090126/f9e4e3e5/attachment.bin>