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

Allowing stale DNS results

· 52CE 我爱测

Is there any method of allowing stale DNS results to be returned? By stale, I mean, where the TTL has expired, but no new record can be obtained, likely due to the nameserver being unavailable. To my knowledge, at least bind 9 do…

问题原文

原帖链接 · Danny F · CC BY-SA 3.0

Is there any method of allowing stale DNS results to be returned? By stale, I mean, where the TTL has expired, but no new record can be obtained, likely due to the nameserver being unavailable.

To my knowledge, at least bind 9 doesn't have any mechanism for this. I also wasn't able to find any reference for it in bind 10. For the life of me, I can't figure out why. There's no reason why DNS couldn't use the same caching rules and methodology that HTTP uses. Sites could choose to disable, or tune their caching preferences.

This seems so simple to me, that I'm hoping that I've missed some new development that someone can share with me :)

P.S. I know there are some end user tools that do this (opendns, dnsmasq, etc), but that takes all the control away from the owner of the domain, and forces the end user to make often wrong guesses about how zone files should be cached beyond their TTL.

已采纳解答

原帖链接 · Blaine Elzey · CC BY-SA 4.0

From BIND 9.12 Releaste Notes at https://kb.isc.org/article/AA-01554/0/BIND-9.12.0-Release-Notes.html, this is now available.

"When acting as a recursive resolver, named can now continue returning answers whose TTLs have expired when the authoritative server is under attack and unable to respond. This is controlled by the stale-answer-enable, stale-answer-ttl and max-stale-ttl options. [RT #44790]"

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

资料来源与适用范围

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

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

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