- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: Bv9ARM.ch08.html,v 1.75.18.61 2007/07/09 06:51:13 marka Exp $ -->
+<!-- $Id: Bv9ARM.ch08.html,v 1.75.18.62 2007/09/07 12:48:57 marka Exp $ -->
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="id2593136"></a>Incrementing and Changing the Serial Number</h2></div></div></div>
<p>
- Zone serial numbers are just numbers — they aren't date
- related. A lot of people set them to a number that represents a
- date, usually of the form YYYYMMDDRR. A number of people
- tested these numbers for Y2K compliance and set the number
- to the year 2000 to see if it would work. They then tried to restore
- the old serial number. This caused problems because serial
- numbers are used to indicate that a zone has been updated. If the
- serial number on the slave server is lower than the serial number
- on the master, the slave server will attempt to update its copy of
- the zone.
+ Zone serial numbers are just numbers — they aren't
+ date related. A lot of people set them to a number that
+ represents a date, usually of the form YYYYMMDDRR.
+ Occasionally they will make a mistake and set them to a
+ "date in the future" then try to correct them by setting
+ them to the "current date". This causes problems because
+ serial numbers are used to indicate that a zone has been
+ updated. If the serial number on the slave server is
+ lower than the serial number on the master, the slave
+ server will attempt to update its copy of the zone.
</p>
<p>
Setting the serial number to a lower number on the master
projects / thirdparty / bind9.git / commitdiff
