tailscale / tailscale

The easiest, most secure way to use WireGuard and 2FA.
https://tailscale.com
BSD 3-Clause "New" or "Revised" License
17.57k stars 1.34k forks source link

Tailscale breaks WSL1 DNS resolution due to ipv6 entries #10425

Open muchcharles opened 7 months ago

muchcharles commented 7 months ago

What is the issue?

Using WSL1, tailscale's ipv6 DNS entries make it into resolv.conf and prevent it from resolving domain names

Steps to reproduce

Install WSL1 and tailscale, happens even with magicDNS turned off.

These entries aer what seem to be breaking it:

Get-DnsClientServerAddress

InterfaceAlias Interface Address ServerAddresses Index Family


Tailscale 44 IPv4 {} Tailscale 44 IPv6 {fec0:0:0:ffff::1, fec0:0:0:ffff::2, fec0:0:0:ffff::3}

They show up in the resolv.conf on WSL1 and nslookup of a domain fails with:

communications error to fec0:0:0:ffff::1#53: timed out

Uninstalling tailscale and restarting WSL fixed it and removed the entries.

Are there any recent changes that introduced the issue?

Suddenly happened recently.

OS

Windows

OS version

Windows 10 Pro

WSL1

$ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.2 LTS Release: 22.04 Codename: jammy

Tailscale version

1.44.2

Other software

WSL1

Bug report

No response

DentonGentry commented 7 months ago

May I ask why not use WSL2?

muchcharles commented 7 months ago

May I ask why not use WSL2?

native windows filesystem performance (git unusably slow on large projects like unreal engine, chromium, firefox, etc. when developing for windows but managing git through WSL instead of windows git's bash)

stuckj commented 3 months ago

This affects me as well. For me, it's a gaming machine that I use for work on occasion as well (when I need more processing power). WSL 2 hurts gaming performance and makes VMs significantly slower so WSL 1 it is.

mrsshr commented 2 months ago

I use WSL1 because I use software that is not compatible with Hyper-V. It would be great if this could be fixed.

$ cat /etc/resolv.conf
# This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:
# [network]
# generateResolvConf = false
nameserver fec0:0:0:ffff::1
nameserver fec0:0:0:ffff::2
nameserver fec0:0:0:ffff::3
search tail.ts.net

$ sudo ping www.google.com
ping: www.google.com: Temporary failure in name resolution
mback2k commented 3 weeks ago

I am experiencing the same issue and would like to see a fix.