Closed W1BTR closed 2 months ago
Does this happen with the alpha, if it does not, I would think this is the same issue as https://github.com/juanfont/headscale/issues/2026
I'm not using the custom nameservers mentioned in that issue (setting a custom ip for a domain in the headscale config), but it might be related.
Ill try in the alpha and report back this week.
Can confirm, alpha-12 does not have this issue.
Is this a support request?
Is there an existing issue for this?
Current Behavior
When connected to an exit node that is routing all traffic through said node, I cannot access the public internet as DNS does not work.
If I disable Tailscale DNS
Note I am only able to test this with the exit node on windows and the client running android.
Expected Behavior
Using the tailscale dns, my headscale server should route traffic to 1.1.1.1 as is in the config.
Steps To Reproduce
Environment
Runtime environment
Anything else?
No response