DNS transfer time within Jodo

timruns

timruns

Perch
OK -- I sorta think this will be a very speedy resulting in just a minute or two of downtime for the client...
I have a client, blahblah.com hosted as an aliased domain under my service account, located on win12. I am moving them to their own account, which is now located on win18. The DNS servers for both is ns3/ns4. So, when it comes time for me to delete the blahblah.com account under my service account, and then add it to the new account, the total down time should be the time it takes me hit 'delete' on one control panel, 'add' on a second control panel, and a diligent Jodo employee to clear the cache on ns3/4. Am I missing something in how the DNS works?
 
You'll have some ISP caching for a little while (few hours usually) but that's something out of yours and Jodo's control.
 
even though the nameservers themselves never change?
Do the DNS servers around the world list the name servers, or do they list the IP address of, for example, the win18 server the client site resides on?
If they only list the nameservers (ns3 and ns4) then it is only the name servers (at Jodo) we have to worry about and we can (via Jodo personnel) make that a fast refresh.
 
Yep even though you don't change nameservers. If you changed nameservers it would be even longer. Most ISP's cache requests to speed up connections for their clients. Usually most are cleared in an hour or so but I have seen some no name ISP's take up to a day. Most nameservers hold the ip address information of the site in their cache. They only go to Jodo's nameservers, when they don't have the information in their cache or their cache has expired. Most people shouldn't see much but you will have some people see the downtime.
 
You must log in or register to reply here.
Back
Top