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

Selfhosted

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

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

[–] Croquette@sh.itjust.works 5 points 4 months 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 4 months ago* (last edited 4 months 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 4 months 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 4 months 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 4 months 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.

[–] Klajan@lemmy.zip 2 points 4 months 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

[–] paequ2@lemmy.today 1 points 4 months ago

Because I'm an idiot. 🤦 Thanks!