Only idea I have is based on a corporate world scenario:

Credentials to log in to the registrar were shared via in house password vault. The email on file with the registrar was a distribution list. Distribution list could never fall below 2 active employees.

On Fri, Feb 20, 2026 at 12:04 PM Billy Croan [email protected] wrote:

Any suggestions on a true multiparty registrar with no single point of failure? Other than to worry about it generally, do you know of any registrars that solve that problem?

On Fri, Feb 20, 2026, 08:54 [email protected] wrote:

...

Hi, new KCLUG list member here.

I signed up after the KCLUG got a shout out on Garmin's Linux Users Slack channel earlier in the week.

Anyways:

I saw the recent discussion on hosting, and a couple of the comments about single points of failure / 1 contact person made me think to chime in here:

Make sure you folks have a good handle on who owns the domain itself, and ideally find a way to mitigate single point of failure there.

I've been a member of UCLUG (Upstate Carolina LUG, Greenville SC) for probably 20 years, but have been remote since I moved out of state ~11 years ago. Looks like UCLUG domain name itself just got poached and lost when it was not promptly renewed.

I haven't kept up with the very latest, but a lot of the original old guard in that UCLUG have become less active as they've entered retirement, shifted focus, whatever. Aomewhere along the line, the ball got dropped.

I did check whois for kclug, and it looks like it is right in the middle of a renewal. Registrant is hidden, but hopefully its one of you.

Cheers, and hope to make it to a meeting at some point, -Vaughan _______________________________________________ KCLUG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://kclug.org/mailman3/postorius/lists/kclug.kclug.org/

---

KCLUG mailing list -- [email protected] To unsubscribe send an email to [email protected] https://kclug.org/mailman3/postorius/lists/kclug.kclug.org/