ressl wrote: ↑Wed Apr 13, 2022 5:32 pm

Username Taken wrote: ↑Wed Apr 13, 2022 2:50 pm CEO has changed name servers (DNS) due to some issues with the previous name servers. Unfortunately, updating/changing name servers can mean the server is unreachable for up to 24 hours, hence the issues yesterday and this morning. We should be past the worst of it now.

hm, usually before you do something like that, you set the DNS TTL to 5 minutes or maybe 15 minutes if it is no critical service. Then you wait 24 hours, until the information got replicated everywhere, then you do the move and then you set back the TTL to whatever it was. At least this is how I handled moves like that in my previous life...

ressl wrote: ↑Wed Apr 13, 2022 6:43 pm the problem is, that after you cleared your cache, your provider (or the DNS you have entered manually) will still give you the old IP, unless the TTL has expired. Only then the next level is asked and if you are very unlucky, this one has still the old information with a still valid TTL. Only if all the TTLs in the chain up to the root DNS servers have expired, the new information is propagated. That's the reason, why you need to set it to a short time.