What is domain name propagation? For new domain name propagation is a period where you newly registered domain being sent to all name servers (or DNS servers) in the world.
DNS server caches of your domain name mapping to IP address. This mapping record normally stored for time period to prevent querying or lookups. For example www.datakl.com resolves to 126.96.36.199 and stores in DNS servers around the world for 6 hours.
DNS servers drop stale DNS record based on few factors such as DNS record timing setting and
the practice of flushing records every interval period (normally ISPs)
Your computer stores DNS record for faster browsing to eliminate frequent DNS query to DNS servers.
The caching is beneficial for faster browsing but if you are in the midst of change hosting company or server, this process could cause confusion or downtime. Why confusion? In hosting or computing everything is almost instantaneous – upload your html/php coded page you can view instantly but for DNS the only solution is to wait!
On and off explains (After changing name servers I could view my web site for a moment and later turns to page could not be found or referring me back to old hosting server why?)
Normally your computer or router/modem use two DNS servers or more. The first (on) probably responded by a DNS server which has your newly modified record and the (off) page could not be found now could cause by another DNS server that still keeping your old DNS record -(error page could not be found or returning you to your old hosting company)
Just wait for propagation period to compete – normally 48 hours and your web site will resolve properly. Try on your luck by rebooting your computer – normally rebooting will flush the old DNS record in your computer or use ipconfig/flush command if you are using Windows DOS prompt. To have less impact on your operation or visitors, change your DNS during non busy hours is recommended – after office hours.
Did you know that we run DNS clustering for all our shared hosting Accounts? Why DNS Clustering
1. Unified nameserver. We use only a pair of nameservers – ns1.datakl.com and ns2.datakl no matter where your site is hosted. Your addon domain will use the same nameservers as well. That is what we call easy and clean.
2. Or ns1 and ns2 are geographically diverse. Ns1 being hosted in Malaysia responds to DNS query for Malaysia and Asia primarily. Ns2 being hosted in the USA to answer any queries from North America and Europe.
3. 1. 0% downtime due to DNS service being down. If the DNS service is down in the server, the domain DNS will be served by the other servers in the cluster.
4. If a server is down (say being rebooted), and at that point if someone tries to send an email to a domain on that server, they will get a delivery failure message and the mail will not be sent again. This is because the sender’s mail server will assume the domain does not exist. But in case a DNS cluster is setup, the mail server sending the mail will only assume the mail server is down, and hold the mail in its queue to be retried again. No delivery failure report message will be sent.
5. It is easy to transfer domains among servers. The client will not have to change the nameservers used by the domains. The same nameservers can be used to point the domain to the new server. Easy migrations for us to move you to better specifications in the future. Other providers might have to contact you and ask you to dig up your domain control panel login, which might delay migration and causing downtime.
6. Faster recovery from server reboots. If you typed your domain name during maintenance and the DNS was down as well, page could not be found could be cached in your computer. It takes a few hours for your site’s DNS to refresh. This can cause confusion and. If you are hosted in DNS clustering environment, the moment server is up and running you can view your web site immediately.
7. Less work for web server. Our web server only handles web content serving and email. No DNS means less work for web server and fast loading web sites!.
How can you tell? If your current hosted giving out nameservers for example 105.nameserver.com and n106.nameserver.com think again because you are not hosted in clustered environment. The DNS, mail, database and content are hosted in the same server
Case Study: During Taiwan earthquake that ruptured undersea cables, internet connection including dns queries were delayed and timed out. Our USA DNS servers pointed the email towards the right server. Most of client emails got through even though the connections was slow. Other hosting providers email transmission timed out due to DNS record could not be reached. Geographical distance and latency caused their email to bounced back to the original sender.