|
|
 |  |
Re: Question about secondary zone updates...From: listaccount@starionline.com Date: Saturday, September 8, 2001
Time: 10:57:17 amI 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).
Incidentally, Len, I've checked the logs of both servers, they are hosted o=
n
two of our machines maintained by us. No errors, but no record of transfer
activity either.
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?
And again, back to my original post, is there a reason why QDNS defaults ne=
w
zones to 8 hour REFRESH values? Must be something there if QDNS thinks it
needs to be 8 hours. Just trying to learn and understand.
Jeff J.
Starion Systems
=20
> the REFRESH value is the one that tells your secondary server how often t=
o
> 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 ide=
a.
>> So the question now becomes;
>>=20
>> If indeed QDNS uses NOTIFY to "alert" the slave to new info, then why do=
es
>> 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 determine=
s 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 rec=
ord
>>> to (xxx 1 2 3 xxx) to define slave behaviour, where the 1 field tells t=
he
>>> 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 for
>>> 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 of
>>>> 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
|

Return to Digital Point Solutions' Home Page |