4 ms·
If you're homelab'ing then you should be using private IPs to host your services anyway. Don't put them on a public IP unless you absolutely have to (eg port 25
by rbut 3y ago
If you're homelab'ing then you should be using private IPs to host your services anyway. Don't put them on a public IP unless you absolutely have to (eg port 25 for mail).
Use your internal DNS server (eg your routers) for DNS entries for each service. Or if you wish you can put them in public DNS also. Eg. gitlab.myhome.com A 192.168.33.11
You can then access your services over an always-on VPN like wireguard when you're away from home.
Then it doesn't matter if anyone knows what subdomains you have, they can't access them anyway.
- chipsa 3y agoTailscale actually does all of the above for you: does the DNS, can register a LE cert, and provides the always-on VPN to allow access when you're away from home.
- thfuran 3y ago>Don't put them on a public IP unless you absolutely have to Not a fan of ipv6?
- haliskerbas 3y agoWhy not something like https://www.cloudflare.com/products/tunnel/ https://www.cloudflare.com/products/tunnel/ free tier?
- nik282000 3y agoIf your exposed services use authentication and you use strong passwords you are no worse off than any small business but you have the advantage of being a lesser target.