Selfhosted

Wow the responses here are really off at the moment. I'm going to try and help.

So, what you're going to want to do is add all the subdomain A records you need to you DNS (sounds like you're using cloudflare for that, not required, but that should be fine).

Those DNS records are all going to be the same IP record, that's fine.

What you need to do after that, so that you don't have to enter ports is a bit more complicated. For web servers, some kind of reverse proxy like nginx, haproxy, apache, etc is what you need. The term you're looking for is "virtual host".

A virtual host setup is basically one where a reverse proxy looks at the domain name that was used to access the server over HTTP and then uses that to decide what server running on the machine you actually talk to.

It's HTTP that actually is passing along the domain name you used, so if the service isn't HTTP you may or may not be able to do anything depending on the underlying protocol.

So to recap:

1. Set up your DNS records
2. Set up an HTTP reverse proxy
3. Add virtual hosts for each service you added a DNS record for to the reverse proxy (so that the reverse proxy can turn foo.example.com into example.com:xyz -- localhost:xyz in practice, morally example.com:xyz though -- behind the scenes)

So here’s my two cents:

I think that if you have a bunch of services, then you should use caddy or Apache or nginx. doing this in caddy and Apache is not that difficult, but I understand the hesitation (I don’t have much experience with nginx)

If you just want to get something working you could do bookmarks with the http://host.whatever.com:port and that would be Gucci.

You could also use another registrar or name server besides Cloudflare to make URL redirect records. This is like an A record but it also includes a port. This is not a standard type of record, but some places will do it like Namecheap.

Again, if you want to do it the right and best way, then I do think a reverse proxy is the way to go.

If you are only accessing the services while connected to tailscale using the tailscale admin console you can add a nameserver, and then point that to a local DNS resolver. The local resolver can point the URL you want to the IP with the ports you want. I don't know if Synology has DNS resolving apps but that might be an option, otherwise you could run pihole or something similar to achieve this.

Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:

7 acronyms in this thread; the most compressed thread commented on today has 12 acronyms.

[Thread #704 for this sub, first seen 22nd Apr 2024, 18:35] [FAQ] [Full list] [Contact] [Source code]

Tailscale has a feature which assigns you a random network subdomain off ts.net. You can use it to find any system by name. But also you don’t need it. You can usually just access the services via the host name if your client is attached to tailscale and also has open ACLs for the services you are accessing. as far as i know there is no way to do what you are trying to do and I'm not sure why you are trying to do it. if you are trying to make a service public you probably want to use something like cloudflared instead.

You can't reach a Tailscale device from the internet the way you're trying because their IPs are from private ranges reserved for CGNAT use. They're not routable on public internet.

What you want is called Tailscale Funnel but it uses their domain (.ts.net) not yours.

You can also try using a CloudFlare Tunnel but they force you to host your DNS server with them.

Both Tailscale and Cloudflare will be decrypting and re-encrypting your HTTPS traffic so please note that.