this post was submitted on 15 Dec 2025
58 points (96.8% liked)

Selfhosted

53730 readers
560 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

  7. No low-effort posts. This is subjective and will largely be determined by the community member reports.

Resources:

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

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I've been de-googling, de-microsofting, and de-Amazoning my life.

One thing I still use for self hosting is AWS Route 53 for Domain Name Services (DNS).

I don't feel ready to self-host DNS.

Do you all have recommendations for reliable and ethical DNS hosting providers?

Or is self hosting some DNS records less of a big deal than I'm imagining?

Advice on either would be welcome. Thank you!

you are viewing a single comment's thread
view the rest of the comments
[–] stratself@lemdro.id 9 points 2 days ago* (last edited 2 days ago)

Desec.io is a solid option - it allows for various types of records like TLSA and SRV. It can also generate scoped API tokens e.g. for "only TXT records of the _acme-challenge subdomain of example.com" to use in automated cert renewals, so pretty good for granularity. It's also a nonprofit.

I think selfhosting DNS is beneficial when you wanna control your own DNSSEC keys, but you'd need to account for high availability and safety. With that, you could do what's called a "hidden primary + public secondary" setup to protect your master DNS data from the public prying. You can even use 3rd-party services like ns-global.zone as your secondaries for redundancy and to reduce load on your infra, too. I recommend Technitium and their guidance if you wanna get started