Unify DNS resolution between Sockets and QUIC

[CarnaViire]

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

• In both cases name resolution happens in managed code (and preferably by the same code)
• We would have more resilient algorithm that traverses a list of resolved IPs instead of only trying the first, which might not work
• We would be able to improve/extend the algorithm by configuration options discussed in [API Proposal]: Enable DNS Round Robin as a configurable option for SocketsHttpHandler #68967, Consider using Happy Eyeballs or similar in SocketsHttpHandler #26177

That would also help to unify name resolution errors/exceptions, see #82262 (comment), #76644

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

• In both cases name resolution happens in managed code (and preferably by the same code)
• We would have more resilient algorithm that traverses a list of resolved IPs instead of only trying the first, which might not work
• We would be able to improve/extend the algorithm by configuration options discussed in [API Proposal]: Enable DNS Round Robin as a configurable option for SocketsHttpHandler #68967, Consider using Happy Eyeballs or similar in SocketsHttpHandler #26177

That would also help to unify name resolution errors/exceptions, see #82262 (comment), #76644

Author:	CarnaViire
Assignees:	-
Labels:	area-System.Net.Quic
Milestone:	-

[CarnaViire]

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

[liveans]

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