Search Again:

Re: Question about secondary zone updates...

From: Cali
Date: Saturday, September 8, 2001
Time: 11:23:09 am

jeff: that is the "default" value.... you can change it to whatever you
want. You must "play" with the expire value too, because if the zone
expires, the secondary server won't answer.

So just make certain that you allow zone transfers from your secondary
server.

If you need further assistant, just write :)

see you

carlos

> From: <listaccount@starionline.com>
> Reply-To: "QuickDNS Talk" <quickdns-talk@lists.menandmice.com>
> Date: Sat, 08 Sep 2001 12:56:25 -0500
> To: QuickDNS Talk <quickdns-talk@lists.menandmice.com>
> Subject: Re: Question about secondary zone updates...
>=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 id=
ea.
>>> So the question now becomes;
>>>=20
>>> If indeed QDNS uses NOTIFY to "alert" the slave to new info, then why d=
oes
>>> 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 re=
cord
>>>> 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




Messages In This Thread:



Return to Digital Point Solutions' Home Page