joined:Sept 11, 2013
This happens all the time:
- I register a new domain with one of my regular registrars who publishes domain data very quickly
- TTL is set to 1800 for the A records (300 for the "mail" subdomain)
- I use several worldwide DNS propagation check sites and a few traceroute servers (in several countries) to confirm that DNS recognises the new domain
- I can see the website I uploaded and successfully send and receive messages via the new domain
- A DAY LATER a client (using a different provider than myself) tells me that their browser cannot find the new domain
I can understand how, after a domain has been moved to a different server, thanks to domain name information caching on part of PCs and on part of providers, a connection request from a browser may for a while be directed to an old IP address, but I don't understand why a provider cannot find a new domain.
Here is an explanation - copied from another thread - of how the DNS works:
If the information for example.com is not cached locally, the browser sends a request to their DNS server asking for the IP address for example.com.
If that DNS server does not have that information, it forwards the request to a higher tier DNS server. (This may continue for a few more tiers depending on how the respective DNS servers are setup.)
If none of the DNS servers have the information, the request finally gets to a top level DNS server that sends the request to your nameserver.
Your nameserver replies with [the IP address] and the information gets sent back down the chain until it eventually gets back to your browser.
After the initial request, the information is stored at each DNS server for a certain period of time.
Why does this not work in some cases?