Why DNS Changes Take Time (and How to Check Progress)
Find out why some people see your new site and others still see the old one, how long it really takes, and how to check without guessing.
TTL 3600 → remembered for 1 hour TTL 300 → remembered for 5 minutes Nameserver change: allow up to 48 hours
🧰 What you need first
- A DNS change you've just made
🎯 What you'll learn
- Understand caching and TTL
- Know realistic wait times
- Check what different parts of the world see
🛠 Tools needed
- A web browser
- Your computer's command line (optional)
It's about memory, not speed
When someone visits your domain, their computer, their internet provider and other servers along the way all remember the DNS answer for a while. That memory is called a cache. Until it expires, they keep using the old answer.
TTL (time to live)
How long, in seconds, other computers may remember a DNS answer before asking again. 3600 means one hour.
Realistic wait times
- Changing a record (A, CNAME, MX): usually as long as the old TTL, often minutes to a few hours.
- Changing nameservers: often a few hours, but allow up to 48 hours.
- A brand-new domain: usually works within an hour of setup.
Note: during the wait, it's normal for you to see the new site while a friend still sees the old one.
See what the world sees
- Use an online DNS propagation checker. Search for "DNS propagation checker", enter your domain and pick the record type (A for a website). It shows answers from servers around the world.
- Ask a public DNS server directly from your computer. These skip your provider's cache:
nslookup example.com 1.1.1.1
nslookup example.com 8.8.8.8
If both show your new IP, the change is live for most of the internet.
For your own computer
- Open the site in a private window so your browser's cache isn't used.
- Clear your computer's DNS cache. On Windows, open Command Prompt and run the command below.
- Try your phone on mobile data instead of Wi-Fi to see a different provider's answer.
ipconfig /flushdns
Tip: planning a move? Lower the TTL to 300 a day ahead. Then the real switch spreads in minutes, not hours.
Common problems
It's been 2 days and nothing changed
Why: The change probably wasn't saved, or it was made at the wrong DNS provider.
Fix: Check which nameservers your domain uses and make the change there.
Some pages show the new site, others the old one
Why: Your browser is mixing cached files.
Fix: Use a private window or clear your browser cache.
Key takeaways
Keep going
- Set up an extra address like blog.example.com: Setting Up Subdomains
Enjoyed this guide?
Support free learning at mC0de.
