this post was submitted on 03 Sep 2026
10 points (91.7% liked)

homelab

10651 readers
32 users here now

founded 6 years ago
MODERATORS
 

I've started a homelab a few months ago, and since then it looked more or less like this:

  • DNS server - with one wildcard record "*.srv.lan" pointing to my reverse proxy (I don't have a proper domain yet)
  • Proxy (traefik) - forwards the requests to specific services (nas.srv.lan -> NAS, photos.srv.lan -> Immich etc.)

An issue showed up when I got around to setting up samba, where because I have a single wildcard DNS record, and the proxy runs on http(s), I cant forward SMB requests to the server, other than using its ip. The same issue arose when I wanted to get dns-based ssh working (even though I have nas.srv.lan set up, ssh-ing that gets me onto the proxy instead of the nas, which makes sense with the dns setup)

One solution that came to my mind would be making each service (I'm using vms, so each service is a different host) have a separate reverse proxy, as well as making the DNS server have all the records separately (nas.srv.lan -> NAS ip, photos.srv.lan -> Immich ip etc.) and then perform the proxying on the hosts. That would lead to me having a dozen different reverse proxies, wasting resources and making managment more difficult.

Are there any other things I could try?

you are viewing a single comment's thread
view the rest of the comments
[–] ohshit604@lemmy.halstead.host 1 points 12 hours ago

As another person mentioned, you typically wouldn’t reverse proxy SMB or SSH, you’re more likely to use SRV records for these services opposed to A records.