3 ms·

I've always thought about expanding on this and just keeping a constantly-updating cache of any DNS requests I make (Where the system keeps them and serves them

by avh02 10y ago

I've always thought about expanding on this and just keeping a constantly-updating cache of any DNS requests I make (Where the system keeps them and serves them even after expiry if not updateable). The only problem is this seems be a tough one to get right config-wise and I just haven't had time to figure it out. Anybody know of any good tutorials for this specific use case? I've googled it a few times and they never seem too easy.

sangnoir 10y ago
> Anybody know of any good tutorials for this specific use case? I've googled it a few times and they never seem too easy. While it's not exactly what you're looking for, you could use dnsmasq, you could use the "--min-cache-ttl" option to increase the TTL: but only up to an hour. You can patch the source to increase this time to suit your needs. To exactly match your use-case dsnmasq would need to have a regular cache that respects upstream TTLs and a last-resort cache that doesn't.