DNS propagation is the way in which the changes you have made to the DNS, or A records, CNAMEs, or the implementation of new name servers, are distributed around the world-wide network of ISPs, or Internet Service Providers. One way to understand this is through the analogy of the ‘update alert’ being sent around town to all the address books in the neighborhood. What this means is that depending on the time frame the different ISPs take to change their records, visitors may view the new settings right away, or the old server information may still point to your site.
Typical Time Ranges
The length of time of propagation is primarily determined by the nature of change you are implementing:
· DNS Record Changes (A, CNAME, TXT): If you are retaining the same name servers and only changing the IP address, you may view the changes within 5 to 30 minutes. However, it may take up to 24 hours depending on the settings.
· Nameserver Changes: If you are migrating the DNS management to new nameservers (for instance, moving to Cloudflare DNS), the propagation generally takes between 2 to 6 hours. However, for worldwide propagation, it usually takes between 24 to 48 hours.
· Worst-Case Scenarios: On some occasions, some regional ISPs might take up to 72 hours to remove their old records.
What Controls the Speed?
The main determining factor for the speed of propagation is the value of TTL (Time To Live) you’ve set for your records. This will tell the DNS resolver to cache that information for how long, in seconds, before checking for any changes. A long TTL (such as 86,400 seconds=24 hours for each record prior to implementing the change you’re trying to make) means that propagation will take a while, or you might go for a shorter TTL, but some ISPs will cache results for any value of TTL, meaning the results will actually be cached for much longer than specified. The best approach is to make your changes and leave them; flipping will result in conflicting information being cached, which will seem like propagation is in an endless cycle.
How to Monitor and Troubleshoot
While this is happening, you should be able to test this on other networks. For example, you might test your site without being on your home WiFi connection. Or you might test this on a cellular connection. To test this manually on your laptop or desktop computer, you might change your DNS resolver from the default one on your computer to the one that Cloudflare uses (1.1.1.1), Google (8.8.8.8). If it works on one but not the other, this is just a sign that theDNS propagation is not finished.
If it has been more than 48 hours and it’s still down across a variety of networks, then it’s no longer a propagation issue. At this point in the process, you want to ensure that your records are in fact correctly listed and that you are actually trying to update them in the right dashboard (Cloudflare vs. Registrar).