Question about secondary zone updates...

Re: Question about secondary zone updates...

From:

Date:

Time:

yes, It is possible. Just increment the serial yourself and you are done.

See you.

Carlos=20

> From: "Mat Robertson" <mathewr@html.net.au>
> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Date: Sun, 9 Sep 2001 15:55:13 +1000
> To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Subject: RE: Question about secondary zone updates...
>=20
> Omce again, I am new here, and just learning about DNS and it wonders,
> however ...
>=20
> I was under the understanding that the REFRESH parameter (field 2) set th=
e
> time between updates, and the RETRY parameter (field 3) set the time dela=
y
> between update retries, until the zones were aligned. None of this meant
> anything though until the SERIAL number (field 1) on the Primary zone had
> been incremented. After the SERIAL number is incremented, then at the nex=
t
> Refresh, the secondary would look to the authorative primary for changes,
> and if the SERIAL is found changed and greater, start a zone transfer. Th=
e
> NOTIFY just forces this behaviour but the secondary DNS still needs to
> verify that the SERIAL number has changed.
>=20
> Is it possible that your SERIAL number on the primary zone is not
> imcrementing, and thus not forcing the zone transfer.
>=20
> Mat Robertson
> Technical
> HTMLnet, Sydney Australia.
>=20
> I just checked these figures, and need to know if these are standard acro=
ss
> all platforms and implementations (ie RFC based standards)
> Refresh - 3hours (10800), Retry - 60mins (3600), Expire - 3days (259200),
> MinTTL - 60mins (3600), and TTL - 60mins (3600)
>=20
> Thanks in advance
>=20
>=20
>=20
> -----Original Message-----
> From: quickdns-talk@lists.menandmice.com
> [mailto:quickdns-talk@lists.menandmice.com]On Behalf Of
> listaccount@starionline.com
> Sent: Sunday, September 09, 2001 3:56 AM
> To: QuickDNS Talk
> Subject: Re: Question about secondary zone updates...
>=20
>=20
> I guess that's what I was asking. I can't seem to find anything in the
> documentation that tells you what each of those parameters is, what they
> affect, what is normal (settings wise).
>=20
> Incidentally, Len, I've checked the logs of both servers, they are hosted=
on
> two of our machines maintained by us. No errors, but no record of transf=
er
> activity either.
>=20
> So if I set the REFRESH value to something much lower it should update
> quicker. I guess back to my original question then, if setting this real
> low, won't resources be tied up checking the slave zone more often?
>=20
> And again, back to my original post, is there a reason why QDNS defaults =
new
> zones to 8 hour REFRESH values? Must be something there if QDNS thinks i=
t
> needs to be 8 hours. Just trying to learn and understand.
>=20
> Jeff J.
> Starion Systems
>=20
>> the REFRESH value is the one that tells your secondary server how often =
to
>> perform the updates.
>>=20
>>> From: <listaccount@starionline.com>
>>> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
>>> Date: Sat, 08 Sep 2001 12:23:55 -0500
>>> To: QuickDNS Talk <quickdns-talk@lists.menandmice.com>
>>> Subject: Re: Question about secondary zone updates...
>>>=20
>>> Okay, a little more technical than I expected, but I get the general
> idea.
>>> So the question now becomes;
>>>=20
>>> If indeed QDNS uses NOTIFY to "alert" the slave to new info, then why
> does
>>> my slave server seem to not be updating quickly (not even after several
>>> hours). Do I perhaps have a configuration problem?
>>>=20
>>> Jeff J.
>>> Starion Systems
>>>=20
>>>>> What parameter of a primary (or is it secondary) zone record determin=
es
> how
>>>>> often the slave zone is updated?
>>>>=20
>>>> initial RFC=B4s use the last 1,2,3 fields in last 5 fields of the SOA
> record
>>>> to (xxx 1 2 3 xxx) to define slave behaviour, where the 1 field tells
> the
>>>> slave how often to request the SOA record from the master to check for
>>>> incremented zone serial number.
>>>>=20
>>>> Polling was augmented with a later RFC which defined the DNS opcode fo=
r
>>>> NOTIFY, where the master will send a NOTIFY packet to all a zone=B4s NS
>>>> records, which then in turn so the SOA/serial number check.
>>>>=20
>>>>> What are the pros and cons of updating a secondary more often
>>>>=20
>>>> a slave pulling an SOA record from the master is not a burden.
>>>>=20
>>>>> , or why
>>>>> wouldn't you want it to be somewhat instantaneous on a small number o=
f
>>>>> zones?
>>>>=20
>>>> the NOTIFY facility makes zone updates as close to instantaneous as
>>>> possible.
>>>>=20
>>>> Len
>>>> __________________________________________________________________
>>>>=20
>>>> Men & Mice: QuickDNS - DNS Expert - DNS Training - DNS Consulting
>>>> DNS Classes: Denver Sep.20-21, NYC Sep. 27-28, Toronto Oct. 18,19
>>>> http://MenAndMice.com/DNS-training
>>>>=20
>>>=20
>>>=20
>>=20
>=20
>=20
>=20
>=20

Sales:
888/4-DPOINT

Support:
858/452-3696