platform: tailnet join must not accept DNS#93
Merged
ExtraToast merged 1 commit intomainfrom Apr 17, 2026
Merged
Conversation
Tailscale's --accept-dns=true rewrites /etc/resolv.conf to point only at 100.100.100.100 (MagicDNS). k3s hands that file to pods via the kubelet, and the pod subnet cannot route to Tailscale's in-kernel resolver — every DNS query inside a pod times out (symptom: Flux source-controller logging 'dial tcp: lookup github.com: i/o timeout'). Fix by dropping --accept-dns to false in bootstrap-tailnet.sh. Tailnet hosts are still reachable on their 100.64.* addresses and via `tailscale status`, we just don't inherit MagicDNS at resolv.conf level. If you previously joined with accept-dns enabled, fix the running node with: sudo tailscale set --accept-dns=false
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tailscale's --accept-dns=true rewrites /etc/resolv.conf to point only at 100.100.100.100 (MagicDNS). k3s hands that file to pods via the kubelet, and the pod subnet cannot route to Tailscale's in-kernel resolver — every DNS query inside a pod times out (symptom: Flux source-controller logging 'dial tcp: lookup github.com: i/o timeout').
Fix by dropping --accept-dns to false in bootstrap-tailnet.sh. Tailnet hosts are still reachable on their 100.64.* addresses and via
tailscale status, we just don't inherit MagicDNS at resolv.conf level. If you previously joined with accept-dns enabled, fix the running node with: sudo tailscale set --accept-dns=false