slave dns server time stamp out of sync with primary

[Mark Andrews]

> Does anyone know why our secondary server time stamp on the zones would be up
> dating and not on the primary?  I've checked the serial over and over on the 
> last zone where changes where made and its ok.  On the slave server the zones
>  are updating throughout the day as the time changes does anyone have any ide
> as as to why this might happen? Our primary server is running as normal no pr
> oblems there.
> Thanks

	The time stamps on the master file on the slave reflect the
	last time the slave checked the serial number on the master
	to see if it has been updated.  This will happen roughly
	every refresh second.  If the serial number is still the
	same just the timestamp on the master file is changed.
	Otherwise the zone is transfered and a new master file is
	written which sets the modification time as a side effect.

	The timestamp on the master file is used to expire the slave
	zone when named is NOT running.

	At startup the zone will be loaded from disk then a check
	is made to see if named was turned off for too long.  If
	named was off for too long the zone is then expired and a
	new copy of the zone is transfered.

	Mark


> Glasgow Caledonian University is a registered Scottish charity, number SC0214
> 74
> 
> 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org