Forcing a secondary update...

[Chris Thompson]

On Jan 27 2009, Barry Margolin wrote:

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

If you want to do it purely from the slave server end, then 
"rndc retransfer [zone-name]" would be easier. (Well, assuming you 
are on BIND 9.3 or later.) This tells BIND to forget everything it 
thought it knew about the zone contents, and fetch it from the master(s).

-- 
Chris Thompson
Email: cet1 at cam.ac.uk