Introduction
DNS caching is one of the most misunderstood aspects of web infrastructure. When you update a DNS record and "it is not working yet," the blame usually falls on propagation delays. But the reality is more nuanced: DNS caching happens at multiple layers — your browser, operating system, router, ISP, and the authoritative nameserver all maintain caches with different TTL values. Understanding each layer is the key to debugging DNS issues effectively and knowing why your changes are not visible immediately.
The Browser DNS Cache
Most modern browsers maintain their own DNS cache separate from the operating system. Chrome, Firefox, Edge, and Safari all cache DNS results to speed up page loads. Chrome's cache duration is typically 60 seconds for successful lookups but can vary based on the TTL of the DNS record and Chrome's internal heuristics. To check Chrome's DNS cache, visit chrome://net-internals/#dns. To clear it, click "Clear host cache" or restart the browser. Firefox stores DNS cache in memory and clears it when you restart. Safari uses the system DNS resolver but also has its own caching layer for frequently accessed domains. The browser cache is usually the first place to check when a record change is not visible — a simple browser restart often resolves the issue.
The Operating System DNS Cache
Your operating system caches DNS responses to avoid querying the nameserver for every request. On Windows, check the cache with ipconfig /displaydns and flush it with ipconfig /flushdns. On macOS, check with sudo dscacheutil -cachedump -entries Host and flush with sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. On Linux, DNS caching depends on the resolver in use — systemd-resolved uses resolvectl statistics to show cache stats and resolvectl flush-caches to flush. The OS cache typically respects TTL values but may have a minimum TTL floor (commonly 30-60 seconds) that overrides very low TTLs. This is a common source of confusion when testing with TTL=1 second — your OS may ignore it.
The Router DNS Cache
Many home and office routers run a DNS proxy or forwarding service that caches DNS responses. This is especially common on routers using DNS services like OpenDNS or Cloudflare's 1.1.1.1. Router caches can be persistent, holding onto old DNS records for hours or even days beyond their TTL. To clear the router cache, you typically need to reboot the router or access its admin interface to flush DNS. Some routers do not expose a flush option, making a reboot the only option. If you are testing DNS changes from a home network and seeing stale results, the router is a likely culprit — try testing from a mobile phone on cellular data to bypass the router cache entirely.
The ISP DNS Cache
Your Internet Service Provider operates DNS resolvers that serve millions of customers. These resolvers cache DNS responses aggressively to reduce upstream queries. ISP caches can be the hardest to clear because you cannot flush them directly. When an ISP cache holds a stale record, all customers on that ISP see the old value until the TTL expires. This is why DNS changes sometimes appear to propagate faster in some regions than others — different ISPs have different cache expiry behaviors. Some ISPs ignore TTL values and enforce their own minimum cache duration (anywhere from 30 seconds to 30 minutes). If you are seeing inconsistent results across different networks, the ISP cache is the most likely explanation.
The Authoritative Nameserver Cache
At the top of the chain, the authoritative nameserver (Cloudflare in is-pro.dev's case) does not cache in the traditional sense — it serves the records you have configured. However, Cloudflare's edge network has propagation delay of its own. When you update a DNS record in the is-pro.dev dashboard, the change propagates to all 330+ Cloudflare data centers within seconds. This is significantly faster than traditional DNS providers, which can take 5-30 minutes for global propagation. Cloudflare's instant propagation is one of the key advantages of using is-pro.dev subdomains — what you configure in the dashboard is live globally within seconds, not hours.
Practical Debugging Workflow
When a DNS change is not working, follow this systematic debugging workflow. Step 1: verify the record using a tool that queries authoritative nameservers directly, such as dig @ns.cloudflare.com yourname.is-pro.dev. If the authoritative server shows the correct record, the problem is downstream caching. Step 2: check from a different network — use your phone's cellular data or a VPN. If the record resolves correctly there, the issue is your local network's cache. Step 3: flush caches at each layer — browser, OS, router — in that order. Step 4: if the record still does not resolve, check that your DNS record is syntactically correct (trailing dots, correct record type, no conflicting records). Use the DNS Checker tool on is-pro.dev to see the record from multiple global locations.
Common DNS Caching Myths Debunked
Myth 1: "DNS propagation takes 24-48 hours." This was true in the early 2000s when TTLs were measured in days. Today, with Cloudflare's instant propagation and common TTLs of 60-300 seconds, changes propagate globally in minutes at most. The "48 hours" figure persists because it is a safe worst-case estimate, not a realistic expectation. Myth 2: "Lowering TTL makes propagation faster." Lower TTL means caches expire sooner and re-query sooner, but the initial propagation from the authoritative server is the same regardless of TTL. You lower TTL to prepare for future changes, not to speed up the current one. Myth 3: "Flushing DNS on my computer instantly fixes everything." Flushing your computer's DNS cache only clears your OS-level cache. The browser cache, router cache, and ISP cache may still hold stale records.
Conclusion
DNS caching is a multi-layer system where each layer can independently serve stale data. Understanding the browser, OS, router, ISP, and authoritative layers helps you debug propagation issues systematically. With is-pro.dev's Cloudflare-powered DNS, the authoritative layer propagates instantly — the delays you experience are almost always downstream caching. Armed with this knowledge, you can diagnose and resolve DNS issues in minutes rather than hours.
Key Takeaways
- DNS is cached at five layers: browser, OS, router, ISP, and authoritative nameserver
- Cloudflare (powering is-pro.dev) propagates changes globally in seconds from the authoritative side
- Nearly all "propagation delay" issues are downstream caching at the browser, OS, router, or ISP level
- Always verify against authoritative nameservers first when debugging DNS changes
- Test from a different network (cellular, VPN) to isolate local caching issues
Frequently Asked Questions
Is is-pro.dev really free to use?
Yes, is-pro.dev provides free subdomains for developers with no hidden fees.
What can I host on an is-pro.dev subdomain?
Any legitimate project — portfolios, SaaS apps, game servers, APIs, and more.