I changed my nameserver and host company for my domain 30 hours ago. Now, DNS propagation checks indicate that the correct nameserver is recognized worldwide.

However, browsers on my own machines produce the old site. I tried multiple browsers and multiple devices (Ubuntu and Android), including some that never accessed the site, to make sure that the problem is not caused by DNS caching in the browser or in the machines. Using Hola or Tor as proxy from other countries, I correctly get the new site.

More strangely, some of the browsers occasionally shift between producing the one site or the other.

I suspect my ISP's DNS is giving crazy results, but how could I diagnose that?

Also, strangely, monitor.us is showing the site as going down, then up, several times a day, when as far as I can tell that is not happening. (It is a basic Wordpress site with, for now, no traffic.) That would suggest that monitor.us is also getting strange DNS values. How can I diagnose this?


2 Answers 2


The output of dig any joshuafox.com shows that the TTL for your domain is 604800 seconds or one week. That is an unusually high value and you might want to change it. Expect the propagation of your new configuration to be fully propagated by the end of the week.

  • Wow! Yes, I see your point. I didn't even imagine that TTL might be set that long.
    – Joshua Fox
    Oct 27, 2014 at 9:41
  • 2
    @JoshuaFox For future reference, common values for the TTL range from about 3600 seconds at the low end for domains that you know will likely have some changes coming to 86400 (24 hours) at the high end.
    – Shadur
    Oct 27, 2014 at 9:48
  • 2
    @Shadur "Common" are as well values as low as 60 s, for dynamic DNS applications.
    – glglgl
    Oct 27, 2014 at 12:11
  • 1
    For the registration (i.e. the entries at the root and gtld servers) low TTL is certainly not a desired permanent solution. I doubt that *.dtld-servers.net would be happy if the TLD of the google.com delegation were at a TTL of 5 seconds, say. Oct 28, 2014 at 7:42
  • I second @HagenvonEitzen: there are very good reasons for result caching, reducing latency is not the least. With the quadrillion of requests per second nowadays, most of them requiring DNS resolution, the root and (g)tld servers would just melt. Dynamic DNS is basically using a loophole at the expense of others. Given the prices for a domain including DNS hosting these days, I simply don't see the point. Oct 28, 2014 at 8:39


you may even keep a long time TTL as you did if you want to spare your server from too much refreshing - i take it that you had your reasons to set it that high (i would recommend two days - 3 at a MAXIMUM), but when you're planning big changes like that, always reset it back to a few hours (or minutes!) a week before the server's migration.

It may put a higher load on your server, but trust me, it will keep you away from a large range of problems. Let's say everything is running smooth and quiet after the move. Some time after, you see that one of the machines is not responding the way it should. It may be a hardware bug, new network factor (did you test your application's behavior under the new load-balancers?), a power-related glitch, it could be a LOT of things. In all those scenarios, your ability to make things transparent to the users as quickly as possible by reverting to the old infrastructure will be based in your DNS TTL.

  • Thanks. I didn't set it that high. The hosting/nameserver provider, ipage, apparently did that by default. I didn't imagine that they might have set it so incredible high.
    – Joshua Fox
    Oct 27, 2014 at 19:09
  • Sometimes I think high default TTLs from combined dns/hosting providers are a dirty trick to punish users who move to third-party hosting... Oct 27, 2014 at 22:32
  • @JoshuaFox the whois for your domain still lists ipage.com - are they the new provider?
    – Alnitak
    Oct 28, 2014 at 8:24
  • @Altinak ipage.com is the webhost, and also provide the nameserver. (The registrar is GKG, and the site was hosted at DotEasy until last week.) I have moved email (MX) to Google Apps.
    – Joshua Fox
    Oct 28, 2014 at 12:30

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .