starred/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-01-13 12:50:32 +01:00
Code Issues 98 Packages Projects Releases 10 Wiki Activity

[Bug] Tailscale Exit Node DNS Doesnt Provide DNS #757

New Issue
Closed
opened 2025-12-29 02:23:29 +01:00 by adam · 3 comments
adam commented 2025-12-29 02:23:29 +01:00
Owner
Copy Link

Originally created by @W1BTR on GitHub (Aug 9, 2024).

Is this a support request?

  • This is not a support request

Is there an existing issue for this?

  • I have searched the existing issues

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.

  • I can run nslookups with 1.1.1.1 and google.com and they succeed
  • I cannot ping 1.1.1.1 as it responds with a dns lookup error
  • I can access local devices and internet-connected servers via their ip address

If I disable Tailscale DNS

  • DNS works as expected, but is not under the control of headscale.

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

  1. Set up basic headscale server
  2. set the dns servers in the config
  3. Run an exit node
  4. Connect a device to the exit node with tailscale dns enabled
  5. DNS no worky.

Environment

- OS: Windows 10 & Android
- Headscale version: 0.23.0-beta
- Tailscale version: 1.70.0

Runtime environment

  • Headscale is behind a (reverse) proxy
  • Headscale runs in a container

Anything else?

No response

Originally created by @W1BTR on GitHub (Aug 9, 2024). ### Is this a support request? - [X] This is not a support request ### Is there an existing issue for this? - [X] I have searched the existing issues ### 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. - I can run nslookups with 1.1.1.1 and google.com and they succeed - I cannot ping 1.1.1.1 as it responds with a dns lookup error - I can access local devices and internet-connected servers via their ip address If I disable Tailscale DNS - DNS works as expected, but is not under the control of headscale. 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 1. Set up basic headscale server 2. set the dns servers in the config 3. Run an exit node 4. Connect a device to the exit node with tailscale dns enabled 5. DNS no worky. ### Environment ```markdown - OS: Windows 10 & Android - Headscale version: 0.23.0-beta - Tailscale version: 1.70.0 ``` ### Runtime environment - [X] Headscale is behind a (reverse) proxy - [X] Headscale runs in a container ### Anything else? _No response_
adam added the bug label 2025-12-29 02:23:29 +01:00
adam closed this issue 2025-12-29 02:23:29 +01:00
adam commented 2025-12-29 02:23:29 +01:00
Author
Owner
Copy Link

@kradalby commented on GitHub (Aug 11, 2024):

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

@kradalby commented on GitHub (Aug 11, 2024): 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
adam commented 2025-12-29 02:23:30 +01:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Aug 12, 2024):

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.

@W1BTR commented on GitHub (Aug 12, 2024): 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.
adam commented 2025-12-29 02:23:30 +01:00
Author
Owner
Copy Link

@W1BTR commented on GitHub (Aug 12, 2024):

Can confirm, alpha-12 does not have this issue.

@W1BTR commented on GitHub (Aug 12, 2024): Can confirm, alpha-12 does not have this issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
CLI
DERP
DNS
Nix
OIDC
SSH
bug
database
documentation
duplicate
enhancement
faq
good first issue
grants
help wanted
might-come
needs design doc
needs investigation
no-stale-bot
out of scope
performance
policy 📝
pull-request
Mirrored from GitHub Pull Request
 question
regression
routes
stale
tags
tailscale-feature-gap
well described ❤️
wontfix
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/headscale#757
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?