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.
  • Hossenfeffer@feddit.ukEnglish
    6·
    8 days ago

    Over many years in a huge variety of tech roles, I’d like to add an additional rule:

    • Always schedule an update or re-configuration on a Friday afternoon, preferably during a bank holiday weekend.
  • sh3llcmdr@feddit.ukEnglish
    3·
    9 days ago

    I’ve got lots of stories of “should not have done that now” in IT and I would never publicly admit to any of them. Fair play for getting it all sorted. And respect due (Stouffer the cat style) for falling on your sword!

  • wewbull@feddit.ukEnglish
    3·
    9 days ago

    Thanks for the transparency. It’s appreciated even though you’re doing this of your own volition. I’m grateful for your efforts regardless.

  • Duckxon@feddit.ukEnglish
    3·
    8 days ago

    By the way how can we support financially whoever is hosting/taking car of the server?

  • BeardedGingerWonder@feddit.ukEnglish
    2·
    9 days ago

    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”

    • ᴇᴍᴘᴇʀᴏʀ 帝@feddit.ukEnglish
      2·
      8 days ago

      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.

      • BeardedGingerWonder@feddit.ukEnglish
        0·
        8 days ago

        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.

        • GreatAlbatross@feddit.ukOPMEnglish
          3·
          8 days ago

          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.

  • Flax@feddit.ukEnglish
    1·
    8 days ago

    I demand a full inquiry!!! Heads will roll!!! I actually had to do something other than leech off of a lemmy instance!!!

  • chickenf622@sh.itjust.worksEnglish
    0·
    8 days ago

    Always love a post-mortem write up. We all make mistakes, and sharing this info helps others avoid the same mistakes. Thanks for sharing and recognizing you dun goofed.