WHAT'S NEW
Domains & DNS · GuideGuides › Domains & DNS

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.

📶 Beginner⏱ 6 min🗓 Updated November 17, 2026❤ 0
ttl.txt
TTL 3600  →  remembered for 1 hour
TTL 300   →  remembered for 5 minutes

Nameserver change: allow up to 48 hours
// Before you start

🧰 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)
01 / Start here

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.

02 / How long?

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.

03 / Check

See what the world sees

  1. 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.
  2. 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.

04 / Speed it up

For your own computer

  1. Open the site in a private window so your browser's cache isn't used.
  2. Clear your computer's DNS cache. On Windows, open Command Prompt and run the command below.
  3. 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.

05 / Help

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.

// Recap

Key takeaways

Changes aren't slow; old answers are remembered (cached)
TTL sets how long they're remembered
Record changes often take minutes to a few hours
Nameserver changes can take up to 48 hours
Lower the TTL a day before planned changes
// What's next

Keep going

Enjoyed this guide?

Support free learning at mC0de.

PIX0
</> {} JS 01
0101 </> CSS JS HTML PIX0 const {} 1010 async mC0de function return 0101 <div> 1010 PIX0 CSS JS HTML const {} 0101 mC0de
PIX0 // WORLD OF CODE
PIX0 IS PREPARING SOMETHING AWESOME FOR YOU 0%