Re: shorten cache ttl?

Never use (TTL=0) ;).

Maybe it's the ghosts of "implementations past" speaking, but 0 TTL's
are troubling. I'd recommend never going lower than 300 or 600 (5 or
10 minutes).

Depending on how the TTL's get 'ticked down', records needed for an
iterative search may drop out of the cache before the iteration
finishes.

DNS is pretty nimble, but it doesn't turn on a .10 Euro coin. ;)

At 17:15 +0200 7/1/04, Marten Lehmann wrote:
>Hello,
>
>> Doesn'y apply, "max-cache-ttl" is about existing records.
>>
>> Try "max-ncache-ttl" which according to the documentation :
>> "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."
>
>I was setting both to 0 and restarted BIND (I really stopped BIND
>completely and started it again). The nameservers for .com-delegations
>(e.g. a.gtld-servers.net) respond with the correct NS-records. My
>caching BIND does not.
>
>Regards
>Marten

--
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Edward Lewis +1-703-227-9854
ARIN Research Engineer

"I can't go to Miami. I'm expecting calls from telemarketers." -
Grandpa Simpson.