-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Unify DNS resolution between Sockets and QUIC #82404
Comments
Tagging subscribers to this area: @dotnet/ncl Issue DetailsCurrently, we are mostly using MsQuic's basic name resolution, that would only use the first IP resolved. We agreed previously that we would like to unify Sockets and Quic in terms that
That would also help to unify name resolution errors/exceptions, see #82262 (comment), #76644
|
Triage: optimistically putting to 8.0 as it touches exceptions (#82262) |
There are better ways to solve this other than my PR (#99204) so I closed the PR for now. Here is the msquic issue related to DNS Resolution: microsoft/msquic#1181 |
Triage: we still don't have a full consensus on how exactly this should be resolved and we don't have a direct usage/complains about the current behavior, so punting this. |
Currently, we are mostly using MsQuic's basic name resolution, that would only use the first IP resolved.
We agreed previously that we would like to unify Sockets and Quic in terms that
That would also help to unify name resolution errors/exceptions, see #82262 (comment), #76644
The text was updated successfully, but these errors were encountered: