this post was submitted on 17 Mar 2024
185 points (97.9% liked)

Selfhosted

61578 readers
859 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

I'm currently on the lookout for privacy-respecting domain registrars. What are you guys using and why?

Edit: I've registered my domain with Porkbun. I got a really cool one, it's called reallyaweso.me!

you are viewing a single comment's thread
view the rest of the comments
[–] dan@upvote.au 1 points 2 years ago* (last edited 2 years ago)

how do you manage self-hosted infrastructure?

Manually, mostly.

DNS is handled by my own PowerDNS server using the PowerDNS-Admin web UI. I manually add records as needed. Editing a domain sends AXFRs / IXFRs to the secondary DNS hosts I use (I self-host three PowerDNS servers, plus I have a DNSMadeEasy account for the important domains, although I'll be dropping that at some point since they increased prices over 10x after being acquired by DigiCert. I use acme-dns for Let's Encrypt DNS challenges. I take daily backups of everything, including the PowerDNS database, so restoring the DB after a server failure is not an issue.

I have 28 VPSes for dnstools.ws and those are lightly managed using Ansible (there's really not a lot running on them): https://github.com/Daniel15/dnstools/blob/master/ansible/roles/dnstools-worker/tasks/main.yml, but I do configure the base OS manually. I don't set up new ones often so this has been fine.

I have a few other VPSes (all running Debian) and a home server (running Unraid) that I handle manually. I don't change things often so it mostly hasn't been an issue for me. Stuff just keeps working. I take daily backups.

The Debian systems all have unattended-upgrades installed. The 'main' Debian VPS I've got started as a dedicated server running Debian Sarge (3.1, from 2005) and I've just kept upgrading it over the years. These days it's a VPS that's much cheaper yet way more powerful than the original 2005 dedicated server :)