Denton Gentry

So far as I can tell the problem is an incompatibility within Android between the VpnService addDnsServer\(\) and the PrivateDNS feature. If DNS servers have been added using VpnServiceBuilder.addDnsServer\(\), then...

Noting from an earlier discussion: turning MagicDNS into a recursive nameserver might be a solution to allow its use. That way, in the default opportunistic mode the Android client won't...

I've gotten AOSP to build and run within the Android Studio emulator, allowing more logging to be added. When Private DNS is enabled in its always-on strict mode, where one...

Misc followups: ---- + In strict mode where you tell Android a DNS service name like dns.google, it checks the validity of the certificate it gets back from the DNS...

Setting the tailscale DNS config to use nextdns.io means your DNS queries are being sent in cleartext, which might be fine depending on what you're trying to accomplish. There is...

I've been running Android 11 for some time, and mostly leave Private DNS set to Off at this point. I haven't run into this issue using that configuration. We do...

When Private DNS was working for you previously, was Magic DNS enabled? Was Tailscale supplying the global DNS servers to use?

This is most likely something relating to broadcast/multicast. As a layer 3 network, broadcast/multicast packets don't traverse a tailscale network.

Since this bug was filed, `tailscale file` added a `--conflict=(skip|overwrite|rename)` argument. It defaults to skip, but can be set to `--conflict=overwrite` https://github.com/tailscale/tailscale/commit/5be42c0af1c9c8899e8383b19d7284a058005bd0

To set expectations: this is why the minimum is 3 days. [email protected] has to get involved to set a shorter interval. Could I ask what concern is being addressed by...