The downside to the .ts.net approach is that you need to install multiple TS clients if you want multiple subdomains. Typically one per service.
There are projects like TSD-Proxy that help with that. It makes it so you only use one Docker container instead of having to make a sidecar container for every service.
Then you also have to resolve *.tailnet.ts.net on your LAN’s DNS and that’s it. Unless you ever want to use something other than Tailscale, that is.



It’s actually better. If you get a domain and install a reverse proxy on the server (Nginx Proxy Manager is easy to use) it will help you get free SSL certificates and make subdomain “aliases” so you’ll be able to use
https://service.coolname.com/links. And they’ll have the little shield in browsers and everything.To get the SSL certificates you’ll need an SSL service with an API and access tokens. Most domain registrars are not this fancy unfortunately, but you can delegate your nameservers to a (free) service that can do that. DeSEC.io is a good choice.
You only need this DNS provider to verify the ownership of coolname.com. You do NOT need to put any IP in there.
The Tailscale access is a bit more involved. Here’s the general steps:
http://100.64.x.x:8081(or whatever the admin port is) as well as athttp://[lan ip of the server]:8081.*.coolname.comto the LAN IP of your server.*.coolname.comto the Tailscale IP (100.64.x.x).After that, when you’re at home but NOT connected to Tailscale you will have coolname.com pointing at the reverse proxy via the LAN IP, and when you ARE connected to Tailscale (whether at home or not) it will be pointing to the Tailscale IP and go through the Tailscale VPN. So you’ll be able to use
https://service.coolname.com/all the time everywhere.