Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!JESSICA.STANFORD.EDU!almquist
From: almquist@JESSICA.STANFORD.EDU (Philip Almquist)
Newsgroups: comp.protocols.tcp-ip
Subject: Re:  Domain resolver resets needed
Message-ID: <8903241145.AA04258@ucbvax.Berkeley.EDU>
Date: 23 Mar 89 23:40:00 GMT
References: <tcs@BRL.MIL> <8903231027.aa08575@SEM.BRL.MIL>
Sender: usenet@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 19

Terry,
> The current refresh entry should satisfy this need if the changes are
> expected in advance.  A week before the change, set the refresh
> interval to 24 hours.  Hosts will begin using the 24 hour interval
> when their current info expires.  One day before the change, set the
> refresh interval to something smaller, perhaps 2 or 4 hours.  When the
> change is made, hosts will only be using the wrong addresses for at
> most 2-4 hours.  When things are stable, change back to your normal
> refresh interval.
	The idea is right, but you used the wrong words and therefore
might confuse somebody.  There is a field in the SOA record called the
REFRESH interval, but that is not what you were referring to above.

	What he does want to decrease is the TTLs associated with the
records that are going to change.  Since no record may have a TTL
smaller than the zone MINIMUM TTL (another phrase from RFC 1035), he
may well have to change the zone MINIMUM TTL.

						Philip