IPv6 fallback to IPv4 broken by a8d1d94 in 0.5.0
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 56
- Forks
- 41
- Avg merge
- 2h 38m
- Merged PRs (30d)
- 7
Description
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?
I suspect that this is due to this change in the resolv gem: https://github.com/ruby/resolv/commit/a8d1d9470e6fa050a4d0151bea19b0034e498f70 which is in 0.5.0 of the resolv gem.
Do any of you want to open an issue at https://github.com/ruby/resolv/issues to report this regression, but also see if reverting that change locally fixes your issues?
I think you can test the older version of
resolv.rbthus:gem uninstall --force resolv gem install resolv -v 0.4.0
Originally posted by @satmandu in #10762
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Compare the resolver behavior in resolv.rb from resolv 0.5.0 with version 0.4.0, focusing on the a8d1d94 change and AAAA/A lookup order. Reproduce the failure with broken IPv6 connectivity, then verify that IPv4 fallback works without regressing normal resolution.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100