Skip to content

/go

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

net: new Resolver type does not respect PreferGo #17532

Closed
rsc opened this issue Oct 20, 2016 · 1 comment

Comments

Assignees

@bradfitz bradfitz

Labels
FrozenDueToAge NeedsFix
Projects
None yet
Milestone
  Go1.8
4 participants
@rsc @gopherbot @bradfitz @quentinmit
@rsc
Copy link
Contributor

commented Oct 20, 2016

The new net.Resolver type is nice, but it looks like many of its methods are unaffected by r.PreferGo. For example r.LookupAddr seems not to consult r.PreferGo. We should fix this before releasing the API into Go 1.8.

@rsc rsc added this to the Go1.8 milestone Oct 20, 2016

@rsc rsc assigned bradfitz Oct 20, 2016

@rsc rsc referenced this issue Oct 20, 2016

Closed

net: cgoLookupAddrPTR returns single PTR regardless of number of PTR records #17093

@quentinmit quentinmit added the NeedsFix label Oct 21, 2016

@gopherbot

This comment has been minimized.

Sign in to view
Copy link

commented Oct 21, 2016

CL https://golang.org/cl/31734 mentions this issue.

@gopherbot gopherbot closed this in 40d4be5 Oct 21, 2016

@golang golang locked and limited conversation to collaborators Oct 21, 2017

@gopherbot gopherbot added the FrozenDueToAge label Oct 21, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
You can’t perform that action at this time.