0

NextDNS slow to update

As a software developer I often find myself creating and updating DNS records, and unfortunately NextDNS is noticeably slower than the likes of Google, Amazon, Cloudflare and others when it comes to picking up changes.

A recent example: I've switched NS records and Cloudflare has noticed the change. I can see the new name servers when I ask 8.8.8.8 but NextDNS is holding on to the old records and it's been hours now.

I need some way to purge the cache held by NextDNS. This isn't a caching issue on the client because I'm routing lookups to specific name servers here.

drill ns example.com @8.8.8.8
drill ns example.com @45.90.xxx.xxx

 

I'm not using the caching feature and I can't find any way to purge whatever caching NextDNS is introducing. And this isn't just NS records!

How do I get NextDNS to actually look up the name servers from the domain registrar? 

6 replies

null
    • NextDNs
    • 2 days ago
    • Reported - view

    This is likely because you are using our resolver before updating which puts the record in our cache and not other resolvers. We then respect the TTL. 

      • Paul_D
      • 2 days ago
      • Reported - view

      Unless you've enabled NextDNS' "Cache Boost" feature, DNS resolvers cache records based on what TTL you put in your domain's zone file. You control how long it stays cached. This is how its been since the 80s because its not possible for a domain owner to go and clear all the caches of all their users' DNS resolvers around the globe. (I understand in this case you're just one user with one resolver)

      I have an A record with a TTL of 300s in my personal domaim. I just updated it and, sure enough, within a few minutes the new IP was being returned in queries to my NextDNS profiles.

    • Snow_Giraffe.1
    • yesterday
    • Reported - view

    I'm following up on my previous query about DNS propagation delays. I appreciate the staff response, but I must respectfully disagree with the assertion that "respecting TTL" is standard practice that cannot be improved upon.

    Current Industry Standards

    Most major DNS providers offer cache management features:

    • Google Public DNS provides a public cache flush interface
    • Cloudflare automatically purges caches upon detecting authoritative changes
    • OpenDNS offers CacheCheck for cache inspection and refresh requests
    • Local resolvers (dnsmasq, systemd-resolved, dscacheutil, Windows DNS Client) all provide flush commands

    These aren't exotic features—they're standard offerings from both free and paid services.

    The Business Impact

    This limitation is causing operational issues across my network. When I update DNS records, I can verify changes via Google (8.8.8.8) and Cloudflare (1.1.1.1) within minutes, whilst NextDNS continues serving stale records for hours—sometimes days. This directly impacts my ability to:

    • Deploy infrastructure changes
    • Migrate services
    • Respond to incidents
    • Maintain development workflows

    Switching to alternative DNS providers immediately resolves these issues, which confirms this is a NextDNS-specific limitation.

    My Request

    I'm asking for one of two outcomes:

    1. Confirmation that a cache purge feature will be added to NextDNS's roadmap, with an estimated timeline
    2. A refund for my subscription, as the service lacks functionality that's freely available elsewhere and is causing regular disruption to my operations

    I've been a paying customer in good faith, but I cannot continue using a service that hampers my work when superior alternatives.

      • Paul_D
      • yesterday
      • Reported - view

      Or you could just drop your TTL to 300 and avoid the issue entirely, no longer requiring a new feature to bypass RFC compliance. You could've fixed this yourself in less time you took to write this message.

    • Snow_Giraffe.1
    • 8 hrs ago
    • Reported - view

    After asking a simple question about cache purge functionality - a feature every major DNS provider offers — I received:

    1. A non-answer from staff saying "we respect TTLs" (not the issue I raised)
    2. Condescending lectures from forum randoms about how DNS works
    3. The realization that this forum IS the only support channel for paying customers

    The answer to my question appears to be: No, NextDNS doesn't have cache purge functionality, and no, they won't add it.

    For any developers reading this: NextDNS will cache your DNS records with no way to purge them. When you update records during development, you'll be stuck waiting while Google, Cloudflare, and others have already propagated your changes.

    I've migrated to a provider that understands developer workflows where TTLs aren't always under our control and sometimes changes have to be made after the fact. Not to mention offering actual support channels!

    To NextDNS: Hiding behind community forums instead of providing real support is a choice. Having forum warriors explain DNS basics to your paying customers asking about missing features is also a choice.

    To Paul: Your TTL lecture was neither requested nor helpful. Consider going outside and touching some grass.

    Account cancelled. ✌️

      • Paul_D
      • 2 hrs ago
      • Reported - view

      My TTL "lecture" was required as you don't appear to understand the technology you're working with and are instead trying to smash a square block into a round hole.

      And to correct your post for any developers reading this: NextDNS will cache your DNS records in compliance with the RFCs like every standard DNS resolver will. When doing deployments involving DNS changes, make sure you follow standard IT practise and drop your TTL before starting so your changes propagate across the Internet quickly.

      Again, you could've fixed this issue yourself in about 30 seconds, yet here we are.

Login to reply

Content aside

  • 2 hrs agoLast active
  • 6Replies
  • 117Views
  • 1 Following