Skip to main content
All CollectionsGetting startedWebsite
DNS Propagation: How long do DNS changes take?
DNS Propagation: How long do DNS changes take?

This KBA provides an explanation of DNS propagation, DNS cache, and the difference between name server changes and regular DNS changes.

Updated over a month ago

Although DNS changes are often quick and can take as little as 15 minutes in most cases, DNS propagation can take up to 24 hours to take full effect. In very rare circumstances, it may take up to a full 72 hours for changes to propagate completely.

What is DNS Propagation?

Think of DNS propagation like spreading news. When you make a change to your websites DNS, that news has to be spread to every server on the internet. Some servers get the memo quickly, while others take a bit longer. That’s why, after changing where your website points, it can take some time (usually up to 24 hours) for everyone to see the change. Though in very rare cases, it can take up to a full 72 hours.

What is DNS and Why Does It Matter?

Imagine DNS (Domain Name System) as the Internet’s phone book. It helps your computer find out where to go when you type in a website address like "mycoolsite.com". Instead of remembering complicated IP addresses like "192.168.1.1", DNS lets you just type in a name, and it finds the right server for you.

Name Server Changes vs. Regular DNS Changes

  • Name Server Changes: This is like changing who hosts your phone book. It takes time for everyone to recognize the new host as the official one, which can take up to 48 hours.

  • Regular DNS Changes: These are simpler updates, like changing your phone number in the phone book. This can take a few minutes up to a few hours for everyone to see the change, depending on how long servers are set to remember old information.

DNS Cache: Why Does My Computer Show the Old Site?

DNS cache is like a sticky note your computer uses to remember websites you’ve visited. It saves time, but it can also mean you’re seeing outdated info if changes have been made recently.

Clearing your Local DNS cache can help:

  • Windows: Use Command Prompt to type ipconfig /flushdns.

  • macOS: Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

  • Linux: Depending on your version, you may need to clear browser cache if your system doesn’t store DNS data.

Does something seem wrong? Need Help?

If it feels like DNS changes are taking forever, you can use tools like What's My DNS to check if the updates have reached servers around the world. If something doesn't look quite right, reach out to our support team! We can help diagnose the issue and get things back up and running.

Did this answer your question?