3 ms·
Side note: Tailscale, like WireGuard itself, has problems in iOS with native IPv6 networks which use 464XLAT because WireGuard prefers the A record on a DNS req
by WirelessGigabit 4y ago
Side note: Tailscale, like WireGuard itself, has problems in iOS with native IPv6 networks which use 464XLAT because WireGuard prefers the A record on a DNS request. This breaks when you're being proxied over an IPv6, and that proxy gets dropped. Then you don't receive notifications until the proxy is re-established.
- klysm 4y agoIs there any way to make wireguard behave differently in this scenario?
- WirelessGigabit 4y agoYea. There is code which does the DNS request. If it returns an AAAA prefer that.
- apenwarr 4y ago(Interviewee here) WireGuard itself barely touches DNS, and tailscale as far as I know doesn’t have any code that would change how your external DNS resolution works. What you’re seeing might be a misdiagnosis. If you email tailscale support we’ll be happy to help figure out what happened and if it’s a bug.