DNS propagation: why changes take time Print

  • propagation, ttl, cache, nameservers, dns
  • 0

When you change your nameservers or a DNS record, the change doesn't reach every computer in the world at the same moment. The time it takes for everyone to see the new information is called DNS propagation.

Why it happens

To make the internet faster, internet providers, routers, computers and browsers save (or cache) DNS answers for a while instead of looking them up every time. Until that saved copy expires, they keep using the old information.

How long each copy is kept depends on the record's TTL (Time To Live), which is set in seconds. A TTL of 14400 means up to 4 hours.

How long does it take?

Type of change Typical time
Adding a new record (for example, a new subdomain) Minutes
Changing an existing record Up to the record's TTL, usually a few hours
Changing nameservers A few hours, sometimes up to 24–48 hours

What you might notice during propagation

  • Your site shows the old version on one device and the new version on another.
  • Email arrives at the old server for a while.
  • A browser shows a security warning because the SSL certificate hasn't been issued yet on the new server.

All of this is normal and clears up on its own.

Things you can try

  • Check from a different network, such as your phone with Wi-Fi turned off.
  • Clear your browser's cache, or open a private/incognito window.
  • Restart your computer or router to clear their saved DNS.
  • Use a free online checker such as whatsmydns.net to see what servers around the world are returning.

Planning a move?

If you're moving an existing website or email to us, keep your account at the old host active for at least a few days after changing nameservers. This makes sure no email is lost while the change propagates.

Still not working after 48 hours?

Open a support ticket with your domain name and what you changed. We'll check that the records are correct.


Was this answer helpful?

« Back