You update your A record. You confirm the new IP is correct. You test it from your office and everything works.
Then a customer messages you saying the website still loads the old server.
This is one of the most common support questions in DNS management. The issue is almost never “DNS is broken.” The issue is caching.
Understanding how DNS cache works in 2026 is essential for diagnosing why some users still see the old IP after a DNS change.
Short Answer
Some users still see the old IP after a DNS change because their resolver, ISP, browser, or operating system has cached the previous DNS record and has not yet refreshed it. DNS records are stored temporarily based on their TTL (Time to Live) value. Until that TTL expires, resolvers continue serving the cached result instead of querying authoritative nameservers for the updated record.
In short, DNS changes are not instant everywhere because caching is designed to reduce load and improve performance.
How DNS Caching Actually Works
When a user visits your domain, their device does not always query your authoritative nameserver directly.
The resolution path typically looks like this:
User device → OS cache → Browser cache → ISP resolver → Recursive resolver cache → Authoritative nameserver
Each layer can cache DNS responses independently.
If any layer still holds the previous record, that user will continue seeing the old IP until the cache expires.
What Is TTL and Why It Matters
TTL stands for Time to Live. It is the duration, in seconds, that a DNS record may be cached before it must be refreshed.
• A TTL of 3600 means resolvers may cache the record for one hour.
• A TTL of 86400 means the record can be cached for 24 hours.
When you change a DNS record, resolvers that previously cached the record will not check for updates until the TTL expires.
Lower TTL values allow faster transitions but increase query frequency.
Why Some Locations Update Faster Than Others
Not all users rely on the same resolver.
• ISP-provided DNS servers
• Public resolvers such as Google DNS or Cloudflare DNS
• Corporate DNS systems
• Mobile carrier DNS infrastructure
Each resolver maintains its own cache. If one resolver cached the record five minutes before your update and another cached it fifty minutes before, their refresh times will differ.
This is why DNS propagation appears inconsistent across regions.
Common Causes of Stale DNS Behavior
1. High TTL Values
If your original TTL was set to 24 hours, some resolvers may continue serving the old IP for nearly a full day.
2. Browser-Level Caching
Modern browsers cache DNS results separately from operating systems.
Clearing browser cache alone does not always clear DNS cache.
3. Operating System Cache
Windows, macOS, and Linux systems maintain local DNS caches.
Flushing the OS DNS cache may resolve discrepancies for individual users.
4. ISP Resolver Cache
Even if you flush your local cache, your ISP resolver may still serve stale data until TTL expiration.
This is outside your direct control.
How to Diagnose a Stale DNS Cache Issue
Step 1: Query Authoritative Nameservers Directly
dig @ns1.yournameserver.com yourdomain.com
This bypasses recursive resolvers and confirms what your authoritative server is returning.
If the authoritative response shows the new IP, the change has been made correctly.
Step 2: Query Public Resolvers
Check responses from major public resolvers:
• 8.8.8.8 (Google DNS)
• 1.1.1.1 (Cloudflare DNS)
If they show different results, you are observing resolver-level caching differences.
Step 3: Check TTL Remaining
Use DNS tools that show the remaining TTL value in resolver responses.
If the TTL countdown is still high, the cache has not expired yet.
How to Reduce Stale DNS Impact Before Making Changes
The best strategy is preparation.
If you plan to migrate hosting or change IP addresses:
- Lower the TTL 24–48 hours before the change.
- Wait for the previous higher TTL to expire globally.
- Then make the DNS change.
This ensures faster propagation when the update occurs.
Can You Force Global DNS Cache Clearing?
Not necessarily. You can flush local OS caches and clear browser caches, but you cannot force ISPs or global resolvers to purge cached records immediately.
Resolvers follow TTL rules by design.
Any service claiming instant global DNS clearing is misleading.
Does Stale DNS Affect SEO?
Temporary DNS inconsistencies can affect search engine crawlers if some resolvers still point to an offline or outdated server.
Search engines use distributed crawling infrastructure. If some nodes resolve correctly and others do not, crawl consistency can be temporarily affected.
However, this impact is usually short-lived when TTL values are managed properly.
DNS Caching in 2026: Why It Still Matters
As performance optimization improves and Anycast DNS infrastructure expands, caching remains critical for scalability.
Without caching, every query would reach authoritative servers directly, increasing load and latency.
Caching improves speed and resilience. The trade-off is delayed visibility of changes.
Understanding this trade-off helps avoid panic during migrations.
Final Thoughts
When some users still see the old IP after a DNS change, the issue is almost always stale cache, not configuration failure.
DNS caching exists to improve performance and reduce load. The delay you observe is a byproduct of that design.
The most reliable solution is planning TTL adjustments before migrations and understanding how resolver layers interact.
NameSilo allows you to manage DNS records and adjust TTL values directly within your domain control panel. By planning TTL reductions before infrastructure changes and verifying authoritative responses, you can reduce propagation confusion and minimize downtime during migrations. .png&w=3840&q=75)
.png&w=2048&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)