There are upcoming maintenance events which may impact our services. Learn more

DNS Propagation – Explained Print

  • 1

This guide will help you to get the general information about DNS propagation and provide you with the answers to the following questions:

What is DNS propagation?

When you update the nameservers for a domain, it may take up to 24-72 hours for the change to take effect. This period is called DNS propagation.

In other words, it is a period of time ISP (Internet service provider) nodes across the world take to update their caches with the new DNS information of your domain.

Due to DNS caches of different levels, after the nameservers change, some of your visitors might still be directed to your old server for some time, whereas others can see the website from the new server shortly after the change.

Why does it take up to 72 hours?

Let’s imagine you live in Bari, Italy, and you just have changed the nameservers for your domain that is hosted in Phoenix, USA.

When you open your domain in a web browser, your request is not going to the hosting server directly, it has to pass through several ISP nodes first. So your computer starts by checking local DNS cache, then the request is sent to your local Bari ISP. From there, the request goes to the upstream provider in Rome, Italy, then connects to the ISP in Hamburg, Germany. After that, the request is sent to the first receiving point in the USA – New York, NY and ultimately, to the ISP in Phoenix, AZ. Here is an example of the request trace – the number of ISP nodes and their location will vary in each particular case:

Each of the ISP nodes checks its own cache to see if it contains the DNS information of the domain. If it is not there, it looks it up and saves it in order to speed up the loading next time and to reduce the traffic.

That is why the new nameservers will not propagate immediately – ISPs have different cache refreshing intervals, so some of them will still have the old DNS information in the memory.

NOTE: to make sure it is not your computer cache that has the outdated information, we recommend clearing the cache of your browser and flushing the DNS cache after the DNS change.

 


Was this answer helpful?

« Back

Powered by WHMCompleteSolution