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

Unify DNS resolution between Sockets and QUIC #82404

Open
CarnaViire opened this issue Feb 20, 2023 · 4 comments
Open

Unify DNS resolution between Sockets and QUIC #82404

CarnaViire opened this issue Feb 20, 2023 · 4 comments

Comments

@CarnaViire
Copy link
Member

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

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Feb 20, 2023
@ghost
Copy link

ghost commented Feb 20, 2023

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

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

Author: CarnaViire
Assignees: -
Labels:

area-System.Net.Quic

Milestone: -

@CarnaViire
Copy link
Member Author

Triage: optimistically putting to 8.0 as it touches exceptions (#82262)

@CarnaViire CarnaViire added this to the 8.0.0 milestone Feb 20, 2023
@ghost ghost removed the untriaged New issue has not been triaged by the area owner label Feb 20, 2023
@karelz karelz modified the milestones: 8.0.0, 9.0.0 Jul 18, 2023
@liveans liveans self-assigned this Feb 15, 2024
@liveans
Copy link
Member

liveans commented Apr 6, 2024

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

@ManickaP
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants