shorten cache ttl?
Edward Lewis
edlewis at arin.net
Wed Jun 30 19:27:27 UTC 2004
In the ARM:
max-ncache-ttl
To reduce network traffic and increase performance the server stores negative
answers. max-ncache-ttl is used to set a maximum retention time for these
answers in the server in seconds. The default max-ncache-ttl is 10800
seconds (3
hours). max-ncache-ttl cannot exceed 7 days and will be silently truncated to 7
days if set to a greater value.
max-cache-ttl
max-cache-ttl sets the maximum time for which the server will cache ordinary
(positive) answers. The default is one week (7 days).
At 20:14 +0100 6/30/04, Jim Reid wrote:
>>>>>> "Marten" == Marten Lehmann <lehmann at cnm.de> writes:
>
> Marten> Bind seems to remember the "I didn't find such a record at
> Marten> the authoritative dns" for some time and does not ask the
> Marten> authoritative nameserver again the second time, while
> Marten> djbdns does. I guess BIND uses sort of TTL, but whats the
> Marten> TTL of a non existing record? But even existing entries
> Marten> are cached to long (but maybe according to the TTL of the
> Marten> authoritative nameserver). Can I overwrite the TTL of the
> Marten> authoritative nameservers at my caching nameserver, so
> Marten> that the records expire earlier?
>
>BIND implements negative caching: "remember that the name/class/qtype
>you asked for doesn't exist". How long it remembers those answers
>depends on the data sent by authoritative server. It's usually the
>value of the MINIMUM field of the SOA record for the zone enclosing
>the name that was looked up. Read RFC2308.
--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis +1-703-227-9854
ARIN Research Engineer
"I can't go to Miami. I'm expecting calls from telemarketers." -
Grandpa Simpson.
More information about the bind-users
mailing list