Skip to content

IPv6 fallback to IPv4 broken by a8d1d94 in 0.5.0 #68

@satmandu

Description

@satmandu

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: a8d1d94 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.rb thus:

gem uninstall --force resolv
gem install resolv -v 0.4.0

Originally posted by @satmandu in #10762

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions