From owner-freebsd-hackers Sun Apr 23 11: 5:45 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2]) by hub.freebsd.org (Postfix) with ESMTP id 28BF037B9C2 for ; Sun, 23 Apr 2000 11:05:43 -0700 (PDT) (envelope-from dillon@apollo.backplane.com) Received: (from dillon@localhost) by apollo.backplane.com (8.9.3/8.9.1) id LAA62689; Sun, 23 Apr 2000 11:05:33 -0700 (PDT) (envelope-from dillon) Date: Sun, 23 Apr 2000 11:05:33 -0700 (PDT) From: Matthew Dillon Message-Id: <200004231805.LAA62689@apollo.backplane.com> To: Leif Neland Cc: Evren Yurtesen , Dave Dunaway , freebsd-hackers@FreeBSD.ORG Subject: Re: bind and the limit of serial number ??? References: Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG :You can not be sure your secondary dns servers are picking up your :zonefile, when you update the primary. : You can 'reset' (roll-over) the serial number, but when you do so you have to realize that the secondaries may continue to cache the 'old' version of the zone file all the way up to the expiration time of the zone in the SOA (normally 3-days to a week). For manual updates of the zone file, I recommend using yyyymmdd rather then yyyymmddhhmm, and if you modify it twice in one day just increment the day (and hopefully real time will catch up to it again). For automatic updates (i.e. scripts that update zone files), I recommend simply starting the serial number at 1 and incrementing it on every update. Trying to make the serial number into a date for viewing ease is overrated. -Matt Matthew Dillon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message