-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
DNS resolver returns SocketAddr
which has meaningless port
#2516
Comments
It used to resolve to |
I don't see any mention of SocketAddrV6 supporting zone ID? How is that feature used here? |
The scope ID is another name for zone ID. |
That can't work as zone ID is string while scope ID is integer? |
Closing this as looks like that does have some use even though I don't see how it could be used (but then I havn't really used ipv6). |
DNS resolver returns
SocketAddr
with port even though port would only be meaningful ifservice
is specified for underlyinggetaddrinfo
. However that is not possible as DNS resolver only takesName
as input.I think this should be fixed by changing return value to
IpAddr
instead ofSocketAddr
.Alternatively DNS resolver could be changed to take
service
as input in addition toName
The text was updated successfully, but these errors were encountered: