Skip to content

each_address should resolve for AAAA first #2024

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

Merged
merged 1 commit into from
Oct 3, 2024
Merged

Conversation

packetcat
Copy link

AAAA over A is standards track behaviour as per RFC 6724.

This also matches behaviour on host OSes such as Linux and Windows.

@nightpool
Copy link

this should respect the host system defaults, such as the value of gai.conf on linux

@packetcat
Copy link
Author

this should respect the host system defaults, such as the value of gai.conf on linux

I agree but personally speaking I don't have the ability to implement that logic into resolv.rb. If someone else is interested in implementing that by all means.

@k0kubun k0kubun changed the base branch from trunk to master August 15, 2019 17:26
@shyouhei
Copy link
Member

@akr Do you have any opinions?

@k0kubun k0kubun requested a review from akr December 31, 2019 08:56
AAAA over A is standards track behaviour as per RFC 6724.
@hsbt
Copy link
Member

hsbt commented Oct 3, 2024

I got an approval for this from @akr at https://bugs.ruby-lang.org/issues/20717

@hsbt hsbt merged commit 1b3f18a into ruby:master Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants