<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DNS + Proxy setup for homelab - any help?]]></title><description><![CDATA[<p dir="auto">I've started a homelab a few months ago, and since then it looked more or less like this:</p>
<ul>
<li>DNS server - with one wildcard record "*.srv.lan" pointing to my reverse proxy (I don't have a proper domain yet)</li>
<li>Proxy (traefik) - forwards the requests to specific services (nas.srv.lan -&gt; NAS, photos.srv.lan -&gt; Immich etc.)</li>
</ul>
<p dir="auto">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)</p>
<p dir="auto">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 -&gt; NAS ip, photos.srv.lan -&gt; 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.</p>
<p dir="auto">Are there any other things I could try?</p>
]]></description><link>https://forum.ieu.app/topic/0054e8ea-d916-494b-ae9a-064fd49fd981/dns-proxy-setup-for-homelab-any-help</link><generator>RSS for Node</generator><lastBuildDate>Sat, 05 Sep 2026 19:26:32 GMT</lastBuildDate><atom:link href="https://forum.ieu.app/topic/0054e8ea-d916-494b-ae9a-064fd49fd981.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 03 Sep 2026 07:05:38 GMT</pubDate><ttl>60</ttl></channel></rss>