![\"DNS](\"https:\/\/www.servergigabit.com\/guide\/wp-content\/uploads\/2020\/06\/Screenshot-2025-12-29-123559-300x156.png\")
<\/p>\n<\/p>\n
General DNS Propagation Information. Understanding what happens during the 3 \u2013 4 days propagation period<\/p>\n
When you change your domain DNS settings in your domain registrar control panel . These new settings must propagate throughout the worlds DNS servers. It also means that every ISP ( Internet Service Provider ) must update their DNS records to reflect these new changes. Which in most cases is done automatically every 24 hours , but not always however.<\/p>\n
<\/p>\n
The root name server will query \u201cdomain registrars\u201d several times a day. The root name server will gather this information from the many registrars. Now in existence and update their master records accordingly. Now your ISP must access their Root Name servers and update their General DNS Propagation Information records which resides on their local DNS server. The process is fully automated and most ISP\u2019s will check the Root Name servers for updates every 24 hours. Beware however that some lame ISP\u2019s will delay this process for as much as 2 to 4 days in some cases.<\/p>\n
If that happens, it will no doubt cause additional confusion as everyone else will be reaching your new account on our server except you. This is because your ISP has not updated their General DNS Propagation Information records and or have not cleared their DNS cache. Which means they\u2019ll still be pointing your domain name to your old server. If it\u2019s a new domain you\u2019ve registered , then you\u2019ll receive a blank \u2018Site Not Found Page\u2019.<\/p>\n
<\/p>\n
Every time you access a site from your ISP they cache the URL as well as its associated IP number. If their network is properly setup , these DNS cache records should \u201cExpire\u201d at least every 24 hours . If they did not ( which is often the case ) , you\u2019ll experience this .<\/p>\n
In a large number of cases, it\u2019s the result of an ISP who \u201cDid Not\u201d configure their servers to \u201cExpire\u201d. The DNS cache records at the appropriate intervals. Unfortunately, this adds additional confusion to their clients and especially the ones whom are trying to point their domain name to a new server.<\/p>\n
The DNS propagation process is not limited to ISP\u2019s ! The internet itself must update \/ clear its DNS cache as well. When we say the Internet. We mean the numerous intermediate \u00c2 \u201cpoint of access\u201d you\u2019re routed through before reaching your final destination. For the most part, these intermediate points of access consist of \u201cInternet Routers\u201d and \u201cInternet Caching Engines\u201d. These too, maintain their own DNS cache which assists. Them in routing traffic \/ resolving URL\u2019s to the correct destination IP\u2019s. Don\u2019t worry though as Internet routers are usually faster at clearing their General DNS Propagation Information cache than ISP\u2019s are.<\/p>\n
<\/p>\n
In most cases, the propagation process will take at least 48 hours to complete. The first thing that happens is the \u201cWorld Root Name Servers\u201d will check all lof the various \u201cDomain Registrars for updates\u201d. After the root name server has done this processing, the rest of it is up to the many ISP providers. Who \u201cshould be\u201d updating their DNS records ( at least every 24 hours ) ,but a number of them will not.<\/p>\n
<\/p>\n
It\u2019s perfectly normal for strange things to happen within the 48 hours propagation period ,but sometimes longer. While we could provide a full list of all the anomalies that can occur during the DNS propagation period. We\u2019ll stick to some of the most common scenarios that most people experience.<\/p>\n
This is a classic case of your friends ISP ( who did update their DNS records ) but yours unfortunately did not. As a result, your ISP is still pointing your domain name to the old DNS record, which is your old hosting account. Wait a couple of more days and it if appears that everyone but you can access your new account. Then contact yours ISP and tell them to expire their old DNS cache records.<\/p>\n
In all likelihood, your ISP may be in the process of cleaning their DNS cache and or updating their local DNS server records. During this small interval, it\u2019s normal to fluctuate between the new and old web site. As the old DNS records may not have completely expired from their cache yet. Give it another several hours and it should be fine.<\/p>\n
This can happen for a number of reasons but in most cases. It\u2019s because your new DNS records have not fully completed the propagation process yet. Consequently, you may be trying to access your old email account on your \u201cold server\u201d which you may have already cancelled. Or it\u2019s in a state of DNS flux ,which means it points to the new server one moment . Next ,points back to the old server. Give it some more time and it will eventually settle down.<\/p>\n