Denton Gentry

Actually since the comment about specific requests is from a year ago and no specific requests were raised, we're closing this during the current bug scrub.

https://github.com/tailscale/tailscale/issues/5932 was closed as a duplicate of https://github.com/tailscale/tailscale/issues/2661, which is still open. There is not currently a public API to set Split DNS nameservers.

I think this is resolved.

Tailscale login has been implemented in a web ui, using `tailscale web -cgi`

I'm running into this as well: it initially manifested only when connecting via LTE, not Wi-Fi. A subset of domains would not resolve, notably *.appspot.com (such as gfblip.appspot.com). At the...

TL;DR: have not managed to produce similar behavior with DNS-over-TLS + Ubuntu + Tailscale (which would have been nice as it is much easier to debug). I enabled DNS-over-TLS on...

Noticed something important while out getting take-out. TL;DR: MagicDNS triggers the problem to occur. Once the device is in the problem state, disabing and re-enabling MagicDNS makes no difference. With...

Trying again to reproduce on Ubuntu, with the added detail of enabling MagicDNS to trigger the problem, I still don't see the failure on Ubuntu. With tailscale up and MagicDNS...

Using adb logcat after enabling PrivateDNS with MagicDNS enabled: `12-14 21:28:04.116 1466 1819 D DnsManager: sendDnsConfigurationForNetwork(106, [100.100.100.100], [example.com.beta.tailscale.net.], 1800, 25, 8, 64, 0, 0, dns.google, [])` `12-14 21:28:04.355 1466 1819...

Noting: + [issue report that Google Fi VPN breaks Android Private DNS](https://www.reddit.com/r/ProjectFi/comments/ag273s/fi_vpn_breaks_googles_dnsovertls/), with the most visible system that dns.google says, "Couldn't connect." This is the same symptom seen here. +...