What is the issue?
When a global DNS server is set in the admin interface and "Override local DNS" is enabled, the system still contacts the local DNS server, in addition to the DNS server specified in the admin interface. I expected that when the "Override local DNS server" setting is enabled, the local DNS server would not be used. This occurs in both a web browser (Firefox) and ping.
Steps to reproduce
Tailscale set to allow incoming connections, allow subnets, allow DNS, and run unattended
In admin panel, have a split DNS entry, set global DNS to Cloudflare, and enable "Override local DNS"
Open Wireshark, start capturing, and use filter ip.addr == 1.1.1.1 || ip.addr == 1.0.0.1 || dns
Open Firefox (with its own DoH setting disabled) and browse to a website. Or, run ping google.com
In Wireshark capture, observe simultaneous DNS activity to Cloudflare over DoH (expected) and system default resolver over port 53 (unexpected)
Are there any recent changes that introduced the issue?
No response
OS
Windows
OS version
20H2, build 19042.1645
Tailscale version
1.22.2
Bug report
BUG-7533d3f5ffa515b26e2432d873cb78d0f7f23890d82081c7dd698dc1374a109e-20220422032618Z-9baa754b87e7df4e
What is the issue?
When a global DNS server is set in the admin interface and "Override local DNS" is enabled, the system still contacts the local DNS server, in addition to the DNS server specified in the admin interface. I expected that when the "Override local DNS server" setting is enabled, the local DNS server would not be used. This occurs in both a web browser (Firefox) and
ping.Steps to reproduce
Tailscale set to allow incoming connections, allow subnets, allow DNS, and run unattended
In admin panel, have a split DNS entry, set global DNS to Cloudflare, and enable "Override local DNS"
Open Wireshark, start capturing, and use filter
ip.addr == 1.1.1.1 || ip.addr == 1.0.0.1 || dnsOpen Firefox (with its own DoH setting disabled) and browse to a website. Or, run
ping google.comIn Wireshark capture, observe simultaneous DNS activity to Cloudflare over DoH (expected) and system default resolver over port 53 (unexpected)
Are there any recent changes that introduced the issue?
No response
OS
Windows
OS version
20H2, build 19042.1645
Tailscale version
1.22.2
Bug report
BUG-7533d3f5ffa515b26e2432d873cb78d0f7f23890d82081c7dd698dc1374a109e-20220422032618Z-9baa754b87e7df4e