What is DNS propagation and why can it take up to 72 hours?

Once you set your CNAME record correctly and click Launch you may have to wait up to 72 hours for your page to be live.

The reason for this delay is a process called DNS Propagation which must be finished in order for you page to be visible on the internet.  Propagation takes place inside the system of your Internet Service Providers (ISP). As a result, propagation -- and the amount of time it takes -- is beyond the control of LaunchRock.

What is DNS?

DNS stands for Domain Name Server. When you purchase you domain name from your domain registrar they create a Master DNS record in their Domain Name Servers. Your domain registrar then points to your Web Host's DNS server as the master authority of your domain.

When any outside computer wants to know how to find your website, they first go to the domain registration database to find out who the DNS authority is for your website. Then they visit your DNS provider's servers to find out what the IP Address is for your domain name. From there the computer is redirected to your IP on your Web Host's servers and can display your website (it is this point where browsers are redirected to LaunchRock if you have a hosted page)

What is DNS propagation?

To make viewing the web faster for their customers, ISPs cache all of their DNS records. This caching process is called Propagation.

Caching means that the ISPs read and display websites from their local files instead of looking them up on the Internet each time their customers want to view a website. This is similar, on a massive scale, to the way the browser on your computer caches websites to speed up browsing.

Propagation ultimately speeds up web surfing by

  1. speeding up the return time it takes for a web browser to request a domain look-up and get an answer
  2. reducing the amount of traffic on the web therefore giving it the ability to work faster.

Why does propagation take so long?

The reason it takes so long for your LaunchRock (or any website) to be visible to everyone once you launch it, is that each ISP has an automated process that updates and caches DNS records every few days. Until their cache is reset, it will not display your launched website. There is not any kind of standard for this process, and they can set propagation time anywhere from a few hours up to 72.

Can you speed the process up?

Unfortunately, no. There is nothing that you, LaunchRock or anyone else can do to reduce DNS propagation time. It is simply a case of waiting for this automated process to complete.


Sources: HowStuffWorks  Developer Shed   Register360 



DNS & CNAME

  1. CNAME: General instructions for creating your CNAME record.
  2. A Record: General instructions for editing your A Record
  3. WWW: General instructions for redirecting the cname 'www' to your LaunchRock page.
  4. 123reg.com: CNAME Record Instructions
  5. 123reg.com: A Record Instructions
  6. 1&1: CNAME Record Instructions
  7. 1&1: A Record Instructions
  8. Bluehost: CNAME Record Instructions
  9. Bluehost: A Record Instructions
  10. CloudFlare: CNAME Record Instructions
  11. CloudFlare: A Record Instructions
  12. DNS Made Easy: CNAME Record Instructions
  13. DNS Made Easy: A Record Instructions
  14. DNS Park: CNAME Record Instructions
  15. DNS Park: A Record Instructions
  16. Domain.com: CNAME Record Instructions
  17. Domain.com: A Record Instructions
  18. Domainmonster: CNAME Record Instructions
  19. Domainmonster: A Record Instructions
  20. DreamHost: CNAME Record Instructions
  21. DreamHost: A Record Instructions
  22. Dyn: CNAME Record Instructions
  23. Dyn: A Record Instructions
  24. eNom: CNAME Record Instructions
  25. eNom: A Record Instructions
  26. eurodns: CNAME Record Instructions
  27. eurodns: A Record Instructions
  28. FatCow.com: CNAME Record Instructions
  29. FatCow.com: A Record Instructions
  30. gandi.net: CNAME Record Instructions
  31. gandi.net: A Record Instructions
  32. GoDaddy: CNAME Record Instructions
  33. GoDaddy: A Record Instructions
  34. HostGator: CNAME Record
  35. HostGator: A Record Instructions
  36. Hostmonster: CNAME Record Instructions
  37. Hostmonster: A Record Instructions
  38. IX webhosting: CNAME Record Instructions
  39. IX webhosting: A Record Instructions
  40. Linode: CNAME Record Instructions
  41. Linode: A Record Instructions
  42. (mt) MediaTemple: CNAME Record Instructions
  43. (mt) Media Temple: A Record Instructions
  44. MyDomain.com: CNAME Record Instructions
  45. MyDomain.com: A Record Instructions
  46. myhosting.com: CNAME Record Instructions
  47. myhosting.com: A Record Instructions
  48. Name.com: CNAME Record Instructions
  49. Name.com: A Record Instructions
  50. NameCheap: CNAME Record Instructions
  51. NameCheap: A Record Instructions
  52. Network Solutions: CNAME Record Instructions
  53. Network Solutions: A Record Instructions
  54. No-IP: CNAME Record Instructions
  55. No-IP: A Record Instructions
  56. OVH: CNAME Record Instructions
  57. OVH: A Record Instructions
  58. Pipe DNS: CNAME Record
  59. Pipe DNS: A Record Instructions
  60. Rackspace: CNAME Record Instructions
  61. Rackspace: A Record Instructions
  62. Register.com: CNAME Record Instructions
  63. Register.com: A Record Instructions
  64. Wild West Domains: CNAME Record Instructions
  65. Wild West Domains: A Record Instructions
  66. Wix.com: CNAME Record Instructions
  67. Wix.com: A Record Instructions
  68. Yahoo!SmallBusiness: CNAME Record Instructions
  69. Yahoo!SmallBusiness: A Record Instructions
  70. I need help with the A record. What should I tell my domain host?
  71. I need help with the CNAME record. What should I tell my domain host?
  72. Identifying Your Domain Host
  73. Restricted CNAME Records
  74. What is DNS propagation and why can it take up to 72 hours?

Feedback and Knowledge Base