Force TTL on a Caching Name Server
Dan Mahoney, System Admin
danm at prime.gushi.org
Wed Sep 6 20:12:07 UTC 2006
On Wed, 6 Sep 2006, Elzey, Blaine A (Blaine) wrote:
Note however that it's not possible (but occasionally requested) in BIND
to do the OPPOSITE -- i.e. override SHORT ttls with longer values.
There have been a number of buggy patches that do this over the years.
> max-cache-ttl 300; should do it for cached RRs.
> Blaine Elzey
> LWS VitalQIP
> Lucent Technologies
> BElzey at Lucent.com
> -----Original Message-----
> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On Behalf Of howting at gmail.com
> Sent: Tuesday, September 05, 2006 9:44 PM
> To: comp-protocols-dns-bind at isc.org
> Subject: Force TTL on a Caching Name Server
> Hi everyone,
> I am not sure if this can be done, but I would like to set up a caching name server that only caches results for a maximum of 5 minutes. That is, I would like to override the result's TTL, refresh, retry etc to only 5 minutes. Effectively, the nameserver must do a fresh lookup every 5 minutes.
> Is this achievable in bind? If so, what configuration should I use?
> Thank you.
"We are basically...'Bandwidth Pimps'...Hrmmm...But that's cool man! You see these gold chains? It's all good!"
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
ICQ: 13735144 AIM: LarpGM
More information about the bind-users