FR: Allow sub-subdomains for funnel (or multiple subdomains)

[gabrielrinaldi]

What are you trying to do?

I am trying to replace ngrok with Tailscale.

My app is served into one port and switch routes based on the subdomain. What I would like to do is have aliases that would go into the same route/port so I can switch routes based on the Tailscale.

An alternative would be to spin the app 3 times and have it running in different ports. But I am still limited to 1 domain per device.

How should we solve this?

I think the easiest path would be to add additionally *.hostname.prefix.ts.net by default when starting a funnel.

A more robust approach would allow you do set which sub-subdomains (or even custom subdomains) when starting a funnel.

What is the impact of not solving this?

We can't fully test the application locally using Tailscale. Or share the link with other team members to help test it.

Anything else?

I've tried using NextDNS to solve this problem, but since we don't control the DNS layer on the Tailscale side it does not help since anything ts.net gets resolved before reaching the NextDNS layer.

[Ivsucram]

Bump. +1 for this FR

[DentonGentry]

Please express interest in issues by upvoting the first comment. We have tooling which helps triage and prioritize by including those reactions.

[ilanbiala]

Is there a current workaround to achieve this while this feature isn't yet implemented?