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

Fix resolving IPv6-only hosts #6204

Closed
wants to merge 1 commit into from

Conversation

Hanaasagi
Copy link
Member

@Hanaasagi Hanaasagi commented Nov 2, 2021

What do these changes do?

Fix the threaded dns resolver skip the correct dns response when connecting a IPv6-only host.

It will resolve #6195 .

Are there changes in behavior for the user?

No.

Related issue number

#6195

Checklist

  • I think the code is well written
  • Unit tests for the changes exist
  • Documentation reflects the changes
  • If you provide code modification, please add yourself to CONTRIBUTORS.txt
    • The format is <Name> <Surname>.
    • Please keep alphabetical order, the file is sorted by names.
  • Add a new news fragment into the CHANGES folder
    • name it <issue_id>.<type> for example (588.bugfix)
    • if you don't have an issue_id change it to the pr id after creating the pr
    • ensure type is one of the following:
      • .feature: Signifying a new feature.
      • .bugfix: Signifying a bug fix.
      • .doc: Signifying a documentation improvement.
      • .removal: Signifying a deprecation or removal of public API.
      • .misc: A ticket has been closed, but it is not of interest to users.
    • Make sure to use full sentences with correct case and punctuation, for example: "Fix issue with non-ascii contents in doctest text files."

@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Nov 2, 2021
@Hanaasagi Hanaasagi changed the title fix: fix resolve ipv6 only host. Fix resolving IPv6-only hosts Nov 2, 2021
@Hanaasagi Hanaasagi marked this pull request as ready for review November 2, 2021 06:44
Copy link
Member

@asvetlov asvetlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm asking for the merge blocking until I make some research.
I expect to find time tomorrow, maybe after tomorrow.

Copy link
Member

@asvetlov asvetlov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR!

#6309 has more checks for this bug

if family == socket.AF_INET6:
if not (socket.has_ipv6 and address[3]): # type: ignore[misc]
continue
if family == socket.AF_INET6 and not socket.has_ipv6:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

socket.has_ipv6 is a compile-time flag.
A host can disable IPv6 support at system startup time also.

@asvetlov asvetlov closed this Nov 14, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Connecting to IPv6-only hosts fails with a RuntimeError
2 participants