Comments on: HOW TO: Speed Up DNS Propagation after Changing Host

By: JohnMiller

JohnMiller — Thu, 31 Mar 2011 20:34:14 +0000

My thanks, too, for alerting me to using Open DNS which gave me an immediate site update instead of having to wait for it to come through my ISP’s cache. Brilliant!

By: Deborah

Deborah — Sun, 19 Sep 2010 20:45:17 +0000

Thank you so much. Using the open DNS allowed me to update my site, which was approaching 72 hours to propagate. I am very grateful for your tips!
DeborahÂ´s last [type] ..FRC Honors Quiverfull Adherents in its Values Voters Summit

By: Mathdelane

Mathdelane — Thu, 10 Dec 2009 14:59:38 +0000

It definitely has nothing to do with the software! Heavens! Try to read your previous comments and base my previous response on what you’re ranting about.

Resolve your DNS issues with your host because this is not the right place for pointless rants.

By: JeePee

JeePee — Thu, 10 Dec 2009 14:44:42 +0000

You access the online reservation system on a web url. So if the IP address changes, the url needs to go to the new IP address in stead of the old one. That has nothing to do with the software.

By: Mathdelane

Mathdelane — Thu, 10 Dec 2009 13:01:04 +0000

If you are changing servers and this was about changing hosts, TTL change can only be requested from the previous DNS authority/host as far as I know. Online reservation systems also depend on the software they use but will only function of course when they get back online and most of the time it can’t be immediate. Even large travel agencies simply go offline in cases like you’ve mentioned. However, online reservation systems I assume should auto-update itself since there’s a software that runs it.

By: JeePee

JeePee — Thu, 10 Dec 2009 12:06:37 +0000

Not entirely obsolete because most answers I have found on the web still state that it takes 24 to 72 hours to refresh the DNS service cache.

I am investigating this for a change in IP address (server move) for an online hotel reservation system, where hotel availability is automatically updated by an interface that sits in the hotel. Hence, even a 24 hour period is way to long. We need it to be much shorter, preferably immediately.

It might be very well that there are providers that do it almost instantly, but we better be sure so we need to change the TTL value.

By: Mathdelane

Mathdelane — Thu, 10 Dec 2009 11:47:49 +0000

I know that before hand but at this time and age, your post is already obsolete enough to assume that most DNS caching nowadays are almost immediate. If my ISP or any other ISP caches DNS in less than 24 hrs., the possibility of viewing a website no longer takes more than 24hrs. provided that newly transferred website ‘s DNS record has finally pointed to its new DNS authority. TTL is no longer a big issue at this point because there was one time out of the four times that I’ve transferred host, DNS propagation was almost immediate.

By: JeePee

JeePee — Thu, 10 Dec 2009 10:49:34 +0000

This is nice, but it only resolves your personal viewing of the website that can now be found on another IP address. Visitors of your website from accross the world use different ISP and use different DNS services. So even though YOU change as described in this article, it does not mean that someone in a different city or country benefits from this. They will have to wait until the DNS server THEY use has updated the DNS record that points to your website.

There is a trick to also update that faster. See:
http://www.technologytricks.com/speed-up-dns-propagation/