This was very much a me mistake, so apologies from me.
The long story short, is that we were migrating the domain between accounts.
As the previous DNS records would be wiped during transfer, we made backups, and started the process.
This morning, the “approve transfer” button was lit.
A sensible person would have gone “perfect, lets get this scheduled”.
Instead, I just pressed the button.
Unfortunately, when you transfer, and are keeping continuity, you should always make sure the receiving account is ready to re-apply the settings.
I didn’t, and the receiving account owner was happily asleep.
100% my bad!
All sorted now (hopefully).
There might be some weirdness while DNS updates propagate through the various caches.
I think the lessons learned are pretty obvious:
- Consider how noticeable downtime will be, and schedule with this in mind.
- Check that your counterpart is online when transferring a domain.
- Always schedule a maintenance window, even if you get excited when the button activates.
I will not stand for this! Good job I’m sitting down, eh 😋
Edit: Genuine question - what are you guys like for coverage in general, I kind of saw it fall apart earlier and was thinking “I hope they’re not sitting at work worrying about Lemmy and not being able to do anything about it”
It wasn’t really a coverage issue. Once the sender hit the big button labeled “are you really sure about this?” only the recipient could sort it out.
Sorry, I meant that more as a general side question that had occurred to me earlier when the issue was happening. You guys do a fantastic job, thank you.
We also tend not to fret too much.
We have backups, and while we try to be professional and manage downtime, I think people are pretty understanding.
Good! Genuinely appreciate the effort you all put in to bring us this place!