Re: Reducing the 2560 negative cache default

Funny how that happens - I immediately spotted the issue after posting!
Removed the colon after the Z and its working as expected:


> Zxyz.school.edu:dns1.school.edu:[email protected]:::::300:600::

thanks

On 5/17/10 12:57 PM, " Fletcher       Cocquyt" <[email protected]>
wrote:

> Ok, I am testing this Z record:
> 
> Z:xyz.school.edu:dns1.school.edu:[email protected]:::::300:600::
> .xyz.school.edu:IPofdns1.school.edu:dns1.school.edu.:600
> 
> Ran make ( tinydns-data)
> 
> I test with:
> 
> dig @dns1 xyz.school.edu
> 
> I still see default 2560 value instead of 300 as expected.
> 
> Is that 2560 value cached itself?
> How do I best test updates to min are in effect?
> 
> Thanks
> 
> 
> On 5/17/10 12:46 PM, "Sabahattin Gucukoglu" <[email protected]>
> wrote:
> 
>> On 17 May 2010, at 19:49, Matthew Dempsky wrote:
>>> On Mon, May 17, 2010 at 7:51 AM, Sabahattin Gucukoglu
>>> <[email protected]> wrote:
>>>> The question was, must a Z record be used in order to change the value of
>>>> min (that's Minimum, or in these enlightened times, Negative Cache
>>>> Lifetime)?
>>> 
>>> Yes.  That field is not available with a "." line.
>>> 
>>>> Which begs the question, what does dnscache use "min" for, the former or
>>>> the
>>>> latter?
>>> 
>>> The fields in the Z line go directly into the SOA record.  (Also,
>>> dnscache never touches a data or data.cdb file directly.)
>> 
>> Yes, but I meant, how will dnscache interpret that field when it receives SOA
>> records over the net in response to errors?  Will it actually honour min as
>> it
>> is done by BIND, EG cache the error for that time?
>> 
>> Cheers,
>> Sabahattin

-- 
Fletcher Cocquyt
Senior Systems Administrator
Information Resources and Technology (IRT)
Stanford University School of Medicine

Email: [email protected]
Phone: (650) 724-7485