Why does propagation take so long

During propagation, traffic may come to either location. One person may see the new server while someone else sees the old one. Also, yourdomain. All of this is normal during propagation. They create their own copy of the master record, and access it locally to search for website, each time someone tries to view it.

This procedure speeds up internet activity, reduces the traffic and thus help the ISP work faster. The reason it takes so long for your website to be visible to everyone once you launch it, is that each ISP has their own standard time frame to update the cache DNS record. Until their cache is reset, it will not display your launched website. This can slow propagation down significantly. Anytime you make changes to the authoritative nameserver for your domain, the changes also have to climb the proverbial DNS ladder.

Tip : To avoid unnecessary downtime when switching providers, we recommend waiting 72 hours before deleting records from your previous provider or discontinuing your old service. The higher your TTL is set, the longer propagation will take. For instance, if your DNS record has a TTL of 86, seconds 24 hours and you make a change to the record, all servers will continue to serve end users the old information until the 24 hours is up.

In this case, a lower TTL is advisable. Recommended TTL for domains that make frequent record changes would be 30 to seconds. The lower the better for mission-critical services. DNS Resources There are some useful websites which will help you see this propagation process, and show you when your website should be visible: What's my DNS?

Most commonly you would use this to check if the A Record for your site has propagated out to the rest of the world. If any locations show a red 'X', it means that location does not have any DNS information for the domain name being queried yet.

If it has been longer than 48 hours, your site is not loading, and the two sites above do not show available DNS records, there may be further issues with the configuration of your site. Please contact our support department for assistance with troubleshooting the issue. Add Feedback. Was this article helpful? Yes No. Originally, mail too was handled by the server with the corresponding A record address, but as time went on it became desirable to separate out mail handling. Enter the MX Mail Exchanger record.

The MX record for a domain holds the name not IP address of one or more servers that will accept mail on behalf of that domain. So, the DNS records for the bbc. The A record for cluster1. Once your local DNS server knows where to go to find out about the uk.

Things change.