-
Notifications
You must be signed in to change notification settings - Fork 31
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
IPv6 fallback to IPv4 broken by a8d1d94 in 0.5.0 #68
Comments
Seeing error messages like this after updating to resolv 0.5.0:
This is being reported by people who are able to resolve AAAA dns records for a host but do not actually have IPv6 connectivity to that host. |
(Turning off IPv6 entirely on the system fixes the issue, so maybe this has to do with the link-local ipv6 address confusing the system.) i.e., doing this fixes things: sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.lo.disable_ipv6=1 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Previously A records were resolved first, which was fine for users with broken IPv6 connectivity.
Now however, users with broken IPv6 connectivity are finding connectivity via net/http broken since the connection to a resolved AAAA address fails.
Perhaps this is a net/http bug?
Originally posted by @satmandu in #10762
The text was updated successfully, but these errors were encountered: