Allow Manual DNS Cache Purging (Including Negative Cache) via Dashboard or API
I recently ran into a pretty annoying DNS caching issue with NextDNS.
I created a new DNS record, and while most DNS resolvers were already returning the correct IP addresses, one of my NextDNS endpoints kept returning an empty response.
Here's what I found:
- 45.90.28.0 → NOERROR, but no A records (NODATA).
- 45.90.30.0 → Correctly returned both IPv4 addresses.
- NextDNS DoH, Google DNS, and Cloudflare's authoritative DNS → All returned the correct results.
- Negative cache TTL → Around 1,600 seconds remaining.
I tested both NextDNS endpoints directly over DNS-over-TLS from the same machine, so this wasn't a local DNS cache issue.
It looks like one resolver was still holding onto an old negative cache entry, while the other was already returning the correct result.
The frustrating part is that there's apparently no way to manually invalidate that cache. You either switch resolvers or wait for the TTL to expire.
I'd really like to see NextDNS support manual DNS cache purging.
A few things that would be useful:
- Per-domain cache purging: Clear cached records for a specific hostname without affecting everything else.
- Negative cache purging: Specifically invalidate NXDOMAIN and NODATA responses.
- Dashboard support: A simple button to clear the cache for a domain.
- API support: An authenticated endpoint so developers can integrate cache invalidation into automated deployment workflows.
- Distributed invalidation: Ideally, invalidate cached entries across the relevant NextDNS resolver instances, rather than just one.
I understand that NextDNS runs a distributed DNS infrastructure, and cache invalidation isn't necessarily straightforward.
But I don't think waiting for a negative cache TTL to expire should be the only option, especially when you're deploying new services, setting up OAuth callbacks, or managing DNS records through automation.
Even a rate-limited API that only supports purging individual hostnames would already be extremely useful.
I'm also curious whether there's already an internal mechanism for this that just isn't exposed to users.
Is there any supported way to manually invalidate negative DNS cache entries today? And if not, could this be considered for the dashboard or API?
Reply
Content aside
-
1
Votes
- 10 hrs agoLast active
- 10Views
-
1
Following
