[Dnsmasq-discuss] Per entry TTL override
Olivier Mauras
olivier at core-hosting.net
Wed Apr 2 21:32:17 UTC 2014
On Mon, 2014-03-31 at 12:59 +0200, Olivier Mauras wrote:
> Hello,
>
> Is it thinkable to allow a per entry TTL override system ?
> I have actually two different needs that i'd like to discuss.
> First NXDOMAINS. I'd like to cache NXDOMAIN from some forwarded
> domains to a specific value. Cache time based on default SOA TTL may
> be too long in some cases and requires a manual cache refresh :(
> Easy example:
> Infra team provisions a new server and ping the hostname asked to see
> if it's not already taken - Yes they could act differently
> It's not, so result is cached and will stay for 1H - default SOA TTL.
> Server provisioning takes 10mn, and hostname is still cached as NX for
> 50mn :(
>
> Second is entry override. Some specific DNS entries could have a
> different TTL than the default one - But not globally per entry gives
> much more flexibility :)
>
>
> Would that make sense to have a binding for request replies - like the
> dhcp lua script support - or would this make more sense as specific
> harcoded options? If this makes any sense at all indeed :)
>
>
> Thanks,
> Olivier
>
>
> _______________________________________________
> Dnsmasq-discuss mailing list
> Dnsmasq-discuss at lists.thekelleys.org.uk
> http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Seemed like i had a double neg-ttl declared in my config and my command
line at the same time which make it to not be correctly handled...
Also seems that no matter what neg-ttl is set to, the first NXDOMAIN on
a cold cache, always get the SOA TTL, am i missing something ?
Any feedback on per entry TTL override ?
Thanks,
Olivier
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20140402/671d0c87/attachment-0001.sig>
More information about the Dnsmasq-discuss
mailing list