Mondoze Knowledge Base

Search our articles or browse by category below

General DNS Propagation Information

Last modified: October 8, 2022
You are here:
Estimated reading time: 2 min

General DNS Propagation Information

Understanding what happens during the 3 – 4 days propagation period.

When you change your domain DNS settings in your domain registrar control panel. These new settings must propagate throughout the world’s 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.

Where do the Root Name Servers receive their information from ?

The root name server will query “domain registrars” 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’s will check the Root Name servers for updates every 24 hours. Beware however that some lame ISP’s will delay this process for as much as 2 to 4 days in some cases.

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’ll still be pointing your domain name to your old server. If it’s a new domain you’ve registered, then you’ll receive a blank ‘Site Not Found Page’.

DNS cache and your ISP

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 set up, these DNS cache records should “Expire” at least every 24 hours. If they did not ( which is often the case ) , you’ll experience this.

In a large number of cases, it’s the result of an ISP who “Did Not” configure their servers to “Expire”. The DNS cache records at the appropriate intervals. Unfortunately, this adds additional confusion to their clients and especially the ones who are trying to point their domain name to a new server.

The DNS propagation process is not limited to ISP’s! The internet itself must update/clear its DNS cache as well. When we say the Internet. We mean the numerous intermediate “point of access” you’re routed through before reaching your final destination. For the most part, these intermediate points of access consist of “Internet Routers” and “Internet Caching Engines”.These too, maintain their own DNS cache which assists. Them in routing traffic/resolving URL’s to the correct destination IP’s. Don’t worry though as Internet routers are usually faster at clearing their General DNS Propagation Information cache than ISP’s are.

What to Expect during this 2 to 4 day propagation period?

In most cases, the propagation process will take at least 48 hours to complete. The first thing that happens is the “World Root Name Servers” will check all of the various “Domain Registrars for updates”.After the root name server has done this processing, the rest of it is up to the many ISP providers. Who “should be” updating their DNS records ( at least every 24 hours ), but a number of them will not.

What's going on with my email? When I try to access it.  I receive "host does not exist" or a "cannot authenticate" error message.

This can happen for a number of reasons but in most cases. It’s 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 “old server” which you may have already cancelled. Or it’s 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.

You can check the DNS here.

Visit here to know about how to verify your website before switching over to DNS.

Was this article helpful?
Dislike 0
Views: 62