大网数据广告活动
服务器运维问答

Can a local DNS cache be configured to use stale records when upstream fails?

· 52CE 我爱测

I'm looking for a proxying/caching DNS Linux server, that is able to serve stale (expired) records if it cannot obtain updates from upstream. Bonus points, if it can be configured to use stale record when upstream takes too long,…

问题原文

原帖链接 · Earwin · CC BY-SA 3.0

I'm looking for a proxying/caching DNS Linux server, that is able to serve stale (expired) records if it cannot obtain updates from upstream.
Bonus points, if it can be configured to use stale record when upstream takes too long, and then update the cache asynchronously when/if the response arrives.

The required behaviour is quite similar to proxy_cache_use_stale nginx directive — serve fresh upstream whenever possible, serve whatever you have when upstream is down.

dnsmasq can forcibly extend TTL of cached records, but this fails on both points — clients get stale records with live upstream, and once extended TTL finally expires and upstream is down — clients get nothing.

已采纳解答

原帖链接 · pahaz · CC BY-SA 4.0

I know similar feature in unbound DNS.

From unbound docs:

   serve-expired: <yes or no>
          If enabled, unbound attempts to serve old responses  from  cache
          with  a  TTL of 0 in the response without waiting for the actual
          resolution to finish.  The actual resolution answer ends  up  in
          the cache later on.  Default is "no".

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-11-29)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0 / CC BY-SA 4.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。