Keep a good answer close.
Understand forwarded and authoritative answer caching, TTLs, and what happens when your zones change.
Start with the answer cache
Enable the cache and choose its entry capacity. Cached answers reduce repeated resolution work; their lifetime follows the configured policy and the DNS data.
cache:
enabled: true
size: 10000Your own zones benefit too
Version 1.2.19 adds caching for eligible local authoritative answers, including exact matches, wildcard expansions, NXDOMAIN, and NODATA. Local zones keep priority over upstream cached data. A zone change immediately makes its older cached answers obsolete, and an unchanged zone-file reload can retain its answers.
Inspect and clear
Use dnsctl to see cache statistics and flush the cache when needed. The dashboard and management SDKs also expose cache controls.
dnsctl cache stats
dnsctl cache flushGo deeper
The configuration reference documents TTL limits and cache policy. Release notes describe the boundaries of the new authoritative cache.