Denton Gentry

Split DNS was delivered in the Tailscale 1.8 release several months ago.

Captive Portal at SFO (San Francisco airport) is also reported to be problematic.

https://github.com/tailscale/tailscale/issues/1634 and https://github.com/tailscale/tailscale/issues/1377 are somewhat similar in that they need a way for MagicDNS to detect that it is in an environment where the set of upstream DNS servers it...

We implemented DNS-over-TCP support for all platforms except iOS in 1.26, and for iOS in 1.28.

As far as I can tell, this was resolved by adding DNS-over-TCP support in 1.26. I've checked a number of systems using `systemd-resolved` and don't find any log messages about...

This test flake would have involved the original MagicDNS forwarding path which grabbed UDP packets from wireguard. All platforms now use netstack for MagicDNS, this might not be reproducible any...

This flake was in the original MagicDNS implementation which grabbed UDP packets directly. As of Tailscale 1.28 all platforms now use netstack for DNS, I don't think this test flake...

I think we just released the opposite situation, ssh to tagged nodes which are shared with you: https://tailscale.com/changelog/#2022-08-09-service

https://login.tailscale.com/admin/acls has been set to use 192.168.100.2 and 192.168.100.3 as the global DNS servers: `2022-08-05 06:18:08.845461065 +0000 UTC: dns: Resolvercfg: {Routes:{example.com.:[192.168.100.2 192.168.100.3]} Hosts:9 LocalDomains:[beta.tailscale.net. ts.net. example.com.beta.tailscale.net.]+65arpa}` However this node does...

On the Linux machine: ``` 2022-08-09 22:58:50.59083153 -0400 -0400: ping(100.75.x.y): sending TSMP ping to [cON4Z] phone ... 2022-08-09 22:58:50.59123098 -0400 -0400: [cON4Z] - Sending handshake initiation 2022-08-09 22:58:50.988862337 -0400 -0400:...