You’ve registered your domain name, paid for hosting with a web hosting company, and started uploading your site to the server. If this is all done, why can’t you see your site when you browse to your domain? What is this DNS propagation people keep telling you about? In order to understand DNS propagation, you must first understand a little about how DNS works.

When you set up your website with your hosting provider, they create a master DNS record on their domain name servers. Your domain registrar (the company you paid for the honor of owning your domain name) points to your web host’s DNS server as being the master authority of your domain. When any outside source wants to know how to find your website, they first go to the registration database to find out who the DNS authority is for your website. Then they visit your hosting provider?s DNS servers to find out what the IP address is for your domain name, and from there, your audience can now view your website.

The problem with this whole scheme is that, in order to speed up the rate at which their customers can view the internet, each internet server provider caches their DNS records. This means that they make their own copy of the master records and read from them locally instead of looking them up on the Internet each time someone wants to view a website. This actually speeds up web surfing quite a bit.

Actually reducing the amount of traffic on the web, giving it the ability to work faster. The downside to this caching scenario, and what makes it take so long for your website to be visible to everyone, is that each company or ISP that caches DNS records only updates them every few days.

This is not any kind of standard, and they can set this time anywhere from a few hours to several days. The slow updating of the server cache is called propagation, since your website’s DNS information is now being propagated across all DNS servers on the web. When this is finally completed, everyone can now visit your new website. Being that the cache time is different for all servers, as mentioned above, it can take anywhere from 36 to 72 hours for DNS changes to be totally in effect.

A few measures to help you find out what the error is.

1- check that you have the correct nameserver. Ask support to make sure you have the correct entries.

2- ping your server IP. dns propagation

3- go to so you can test if your domain is now active in other places   in the world.

4-Call l support for further help.

Read about how to deploy Node.js on our servers.