From owner-freebsd-questions Sat Feb 20 11:30:15 1999 Delivered-To: freebsd-questions@freebsd.org Received: from mta1-rme.xtra.co.nz (mta.xtra.co.nz [203.96.92.1]) by hub.freebsd.org (Postfix) with ESMTP id B7F9D11985 for ; Sat, 20 Feb 1999 11:25:53 -0800 (PST) (envelope-from junkmale@pop3.xtra.co.nz) Received: from wocker ([210.55.210.87]) by mta1-rme.xtra.co.nz (InterMail v04.00.02.07 201-227-108) with SMTP id <19990220192615.GHON682101.mta1-rme@wocker>; Sun, 21 Feb 1999 08:26:15 +1300 From: "Dan Langille" Organization: The FreeBSD Diary To: Namodn ROOT , dan@wolf.com Date: Sun, 21 Feb 1999 08:25:52 +1300 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Re: off-site secondary DNS Reply-To: junkmale@xtra.co.nz Cc: freebsd-questions@freebsd.org In-reply-to: <19990220075812.A20511@ns.wolf.com> References: <19990220055521.PZWW3226200.mta2-rme@wocker>; from Dan Langille on Sat, Feb 20, 1999 at 06:54:29PM +1300 X-mailer: Pegasus Mail for Win32 (v3.01d) Message-Id: <19990220192615.GHON682101.mta1-rme@wocker> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 20 Feb 99, at 7:58, dan@wolf.com wrote: > While my knowledge of the specifics is a bit rusty, I > seem to recall that that is precisely the reason for > remembering to implement your serial number each time > you change zone records on the primary machine. THe > secondary will poll the primary at predetermined intervals > (I don't remember *where* it's determined - that's where > the rust sets in) and determine the current serial > number. If he (the secondary) doesn't have the current > version of the data he'll automatically initiate a > named-xfer to get the current records. > > Of course, this assumes that you can afford to wait > for the secondary to get around to checking currency > of his data... Ahh yes, this is correct. I was missing this point. I thought the poster was trying to modify the primary and get that to refresh the boot records. Most people now use a serial number of the form YYYYMMDDHHMM. And the refresh rate determines how often the secondary will check the primary for a more recent serial number. Here's an example of these values from my website: @ IN SOA mydomain.com. root.freebsd.mydomain.com. ( 199902210845 ; Serial 3600 ; Refresh 300 ; Retry 3600000 ; Expire 3600 ) ; Minimum The above shows that I modifed the zone files on 21 Feb 1999 at 08:45. The secondary will compare that serail value to it's own. If the primary contains a newer value, the secondary will request a zone transfer. The secondary will check the primary's serial number every 3600 seconds (every hour). Sorry. I really should have said all this the first time. -- Dan Langille The FreeBSD Diary http://www.FreeBSDDiary.com/freebsd To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message