Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chrome on mac is broken with MagicDNS enabled on an ipv4 only network #14500

Open
mikejobson opened this issue Dec 30, 2024 · 0 comments
Open

Comments

@mikejobson
Copy link

mikejobson commented Dec 30, 2024

What is the issue?

When using Chrome (this issue doesn't present itself with Safari) on a mac, some url's resolve as IPv4 and IPv6 addresses but will then fail to load. If it resolves as IPv4 only then it will work fine. This is only an issue when using MagicDNS

Steps to reproduce

Enable Tailscale with MagicDNS and using Chrome on IPv4 only connection. Some sites do not work at all and some fail to load resources. In my instance I could not open tailscale.com Using chrome://net-internals/#dns test with tailscale.com produces: Resolved IP addresses of "tailscale.com": ["76.76.21.21"]. No alternative endpoints. when not using MagicDNS but with it enabled the same test shows as Resolved IP addresses of "tailscale.com": ["76.76.21.21","2600:9000:a602:b1e6:5b89:50a1:7cf7:67b8","2600:9000:a51d:27c1:6748:d035:a989:fb3c"]. No alternative endpoints.

If you enable MagicDNS with an exit node however it works as IPv6 then works over the exit node.

Are there any recent changes that introduced the issue?

Worked fine for a while until upgrade of various versions of OS or maybe even Chrome.

OS

macOS 15.2

OS version

macOS 15.2

Tailscale version

1.78.1

Other software

Chrome 131.0.6778.205 (arm64)

Bug report

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant