paequ2@lemmy.today 3 weeks ago
Actually, one thing I want to do is switch from services being on a subdomain to services being on a path.
immich.myserver.com -> myserver.com/immich jellyfin.myserver.com -> myserver.com/jellyfin
I’m getting tired of having to update DNS records every time I want to add a new service.
I guess the tricky part will be making sure the services support this kind of routing…
Wildcard CNAME pointing to your reverse proxy who then figures out where to route the request to? That’s what I’ve been doing - this way there’s no need to ever update DNS at all :)
I find the path a bit clunky because the apps themselves will oftentimes get confused (especially front-ends). So keeping everything “bare” wrt path, and just on “separate” subdomains is usually my preferred approach.
In Nginx you can do rewrites so services think they are at the root.
Alternatively if you’re tired of manual DNS configuration:
FreeIPA
Configures users, sudoer group, ssh keys, and DNS in one go.
Also lotta services can be integrated using LDAP auth too.
So far I’ve got proxmox, jellyfin, zoneminder, mediawiki, and forgejo authing against freeipa in top of my samba shares.
Having a very similar infrastructure, I would love to know if you ever find anything that works for this. I’ve been maintaining a SnipeIT instance manually, but that’s a real PITA. Tried the same with ITSM-NG, but haven’t even lookid in it for months.
I had the same idea, but the solution I thought about is finding a way to define my DNS records as code, so I can automate the deployment. But the pain is tolerable so far (I have maybe 30 subdomains?), I haven’t done anything yet
suicidaleggroll@lemmy.world 3 weeks ago
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.
Scrath@lemmy.dbzer0.com 3 weeks ago
Not OP but a lot of people probably use pi-hole which doesn’t support wildcards for some inane reason
Croquette@sh.itjust.works 3 weeks ago
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 3 weeks ago
That wasy 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
Klajan@lemmy.zip 2 weeks ago
It does support it, you just have to add it to dnsmasq. I have it Setup under
misc.dnsmasq_lineslike so:Then I have my proxied service reachable under
service.proxy.example.compaequ2@lemmy.today 1 week ago
Because I’m an idiot. 🤦 Thanks!