this post was submitted on 13 Mar 2026
1326 points (99.0% liked)

Selfhosted

56958 readers
1217 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
 
you are viewing a single comment's thread
view the rest of the comments
[–] suicidaleggroll@lemmy.world 24 points 1 day ago* (last edited 1 day ago) (1 children)

Why are you having to update your DNS records when you add a new service? Just set up a wildcard A record to send *.myserver.com to the reverse proxy and you never have to touch it again. If your DNS doesn't let you set wildcard A records, then switch to a better DNS.

[–] Scrath@lemmy.dbzer0.com 9 points 22 hours ago (3 children)

Not OP but a lot of people probably use pi-hole which doesn't support wildcards for some inane reason

[–] Klajan@lemmy.zip 2 points 9 hours ago

It does support it, you just have to add it to dnsmasq. I have it Setup under misc.dnsmasq_lines like so:

address=/proxy.example.com/192.0.0.100
local=/proxy.example.com/

Then I have my proxied service reachable under service.proxy.example.com

[–] Croquette@sh.itjust.works 5 points 21 hours ago (1 children)

That's my case. I send every new subdomain to my nginx IP on pi-hole and then use nginx as a reverse proxy

[–] Scrath@lemmy.dbzer0.com 1 points 20 hours ago* (last edited 20 hours ago) (1 children)

That was my exact setup as well until I switched to a different router which supported both custom DNS entries and blocklists, thereby making the pi-hole redundant

[–] Croquette@sh.itjust.works 1 points 16 hours ago (1 children)

I run opnsense, so I need to dump pi-hole. But I don't have the energy right now to do that.

Pi-Hole was pretty straightforward at the time and I did not look back since then. Annoying, but easy.

[–] Scrath@lemmy.dbzer0.com 1 points 8 hours ago

I use a MikroTik Router and while I do love the amount of power it gives me, I very quickly realized that I jumped in at the deep end. Deeper than I can deal with unfortunately.

I did get everything running after a week or so but I absolutely had to fight the router to do so.

Sometimes less is more I guess

[–] qjkxbmwvz@startrek.website 2 points 20 hours ago

I switched to Technitium and I've been pretty happy. Seems very robust, and as a bonus was easy to use it to stop DNS leaks (each upstream has a static route through a different Mullvad VPN, and since they're queried in parallel, a VPN connection can go down without losing any DNS...maybe this is how pihole would have handled it too though).

And of course, wildcards supported no problem.