I have four devices in my little tailscale network (a mac, a linux server, an iphone, and a windows 10 box). Magic DNS works just fine on all devices except for the Windows machine, which cannot resolve any of the others’ host names. Resolve-DnsName just times out, as does ping. All other machines, however, have no problem resolving the host names of each other, including the Windows machine’s host name.
I’m not sure how to go about debugging this, to be honest. Can anyone point me in the right direction to get me started?
shows something possibly interesting here. Tailscale isn’t showing any IPv4 values for ServerAddresses, but it does show addresses for the IPv6 entry. After the two entries for the Tailscale interface, there are two for Ethernet, which shows an IPv4 address for my DNS host (a sonicwall router running a DNS proxy cache, which points to 188.8.131.52 for its primary upstream DNS).
In Tailscale, global nameservers are not configured to override local.
No problem browsing the internet when Tailscale is disconnected.
So for others running Tailscale in Windows, what do you see for the Tailscale interface when you run Get-DnsClientServerAddress? Do you see any IPv4 values for ServerAddresses? Or if you’re like me, are you getting something like the following:
Tailscale doesn’t add addresses in that form, I think that is what Windows adds if DHCP times out (though Tailscale interfaces don’t use DHCP at all). Windows would add a 169.254.x.x IPv4 address, an IPv6 link-local addresses, and fec0:0:0:ffff::1 DNS servers.
Using MagicDNS on my Win10 system I could resolve Tailscale FQDNs but not short names.
If I modify the Tailscale Tunnel adapter, IPv4 settings, under advanced settings, DNS I add mydomainname.net.beta.tailscale.net to the "Append these DNS suffixes (in order) field.
Now short and full domain lookups appear to work as they should.
This will stop working when you change the MagicDNS suffix.
edit - on an entirely different machine that is on an isolated network with no DNS suffixes at all specified, MagicDNS short names appear to work correctly on Win10.
On the shortname non-working LAN I have a DNS suffix from DHCP. Now I have both with the local one first and the tailscale one second.