3

It's often the case that I want to change name servers because my site is messed up.

Well, it takes a very long time for the name server to propagate.

Is there something in DNS, or registrar or anything I can do to speed that up.

Flushing my dns server using https://www.whatsmydns.net/flush-dns.html and it rarely works

3
  • Is it a shared host or dedicated host?
    – jjohnson
    Oct 23, 2013 at 16:36
  • dedicated hosts
    – user4951
    Oct 23, 2013 at 16:38
  • do you have root access to the dedicated host?
    – jjohnson
    Oct 23, 2013 at 16:46

3 Answers 3

6

The "time to live" (TTL) on DNS records controls how long it takes for DNS changes to propagate. It is fairly common to set TTL to a low value like 30 or 60 minutes to be able to switch a web service over to a hot spare in case of downtime.

Here is an article about TTL that you may find helpful.

This does require the advanced planning of having already set a shorter TTL well before you have the need to fail over. If you need to fail over right now, you are out of luck. DNS will take as much time as your previous TTL setting.

3
  • I believe that ISPS can set their own TTL however so even with a 1min TTL it doesn't mean that your domain will resolve every where across the world. There's 215 million or more domains in circulation and querying each each domain determined by the TTL for a lot of DNS servers would be overwhelming, there's few websites stating that TTL doesn't necessary reflect quicker prorogation, for example ISPS in the UK may honour the TTL for .co.uk domains but may have a set one for .nl because they believe its less important and resources are best served for popular domains... Not 100% but makes sense. Oct 23, 2013 at 19:08
  • It's true that not all ISPs will honour shorter TTLs, but in my experience the majority do, so lowering TTLs (if your DNS provider supports this) is still good advice for smoother migrations. Oct 24, 2013 at 10:13
  • Default TTLs are usually in the neighborhood of 1 day. Anything 30 minutes or longer should be honored. Half an hour or an hour of downtime is much better than a day if you lower your TTLs to that. Oct 24, 2013 at 11:07
1

I have had great results with https://developers.google.com/speed/public-dns/cache.

My domain name expired I didn't realize until my website had been down for 2 days. I was able to renew it, however, my hosting provider failed to recognize the website was renewed. I gave it 24 hours to "Propagate" as my hosting provider directed. After 24 hours it still was not recognizing DNS for my domain name and rendering my site I plopped my domain name in the above tool and it worked in like 2 minutes.

2
  • It looks like that tool will flush the cache on Google's DNS servers. Since Google is widely used for DNS services, that may help quite a bit, but it isn't going to solve the problem for all of your visitors. Nov 19, 2021 at 15:35
  • To expand on Stephen's comment, I wonder if you tested with a VPN to different locations around the world or you simply used a DNS lookup tool that let you specify different DNS sources if you would get the same results. My guess is no, as some DNS servers have a 24 hour Time to Live (TTL) configurations, meaning they won't query authoritative DNS servers for 24 hours.
    – Trebor
    Nov 20, 2021 at 2:33
0

I recently ran into a similar issue, I couldn't update the live site until my ISP flushed their DNS cache (which was well over the 2hr TTL I had set). What worked for me was using Google's Public DNS https://developers.google.com/speed/public-dns/ It might not cause faster worldwide propagation, but it can allow you earlier access if your ISP is slow to update.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.