The benefits of serving stale DNS entries when using Consul
Mar 8, 2021André Cruz

Summary
This post details the implementation and benefits of serving stale DNS entries from cache using Unbound, improving resilience and reducing latency for Consul service discovery. The configuration of Unbound with `serve-expired: yes`, `serve-expired-ttl: 3600`, and `serve-expired-client-timeout: 500` addresses issues with low TTLs and network blips, ensuring faster recovery times and a more robust service discovery experience. It also addresses previous concerns about Unbound serving indefinite stale records or incomplete information, confirming that current versions and configurations mitigate these issues.
More from the DNS Infrastructure & Naming Conventions trail
- The keys to the Internet change on October 11, 2026. Are you ready?
- 1.1.1.1 now supports post-quantum DNSSEC, all 2,420 bytes of it
- How we saved 100 terabytes of memory by optimizing 1.1.1.1’s DNS cache
- BGP ORIGIN attribute manipulation and its impact on the Internet
- Cloudflare Internal DNS is now generally available