Quote from: ma_bit on October 12, 2013, 04:54:41 PM

Quote from: eleuthria on October 12, 2013, 04:30:56 PM

Invalid certificate errors are expected for people who use DNS resolvers which are still using the cloudflare nameservers. It's been about 18 hours since moving to a new nameserver, ideally you would be updated already. It only took about 4 hours to update on my PC using Google's DNS servers. There's absolutely nothing I can do on my end to fix the cloudflare certificates, it's just a waiting game for your DNS resolvers to use the proper nameservers.

I think you can Wink

... not now, but for next time, you can set shorter validity (or shorter refresh) of DNS records ... but you can have good reason to keep it the same as today

@ IN SOA nameserver.place.dom. postmaster.place.dom. (
   1 ; serial number
   3600 ; refresh [1h]
   600 ; retry [10m]
   86400 ; expire [1d]
   3600 ) ; min TTL [1h]

The problem is a significant number of those settings are completely ignored by ISP level DNS caching/resolvers.