Resolve DnsEndPoint in UdpConnection #1457
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yaakov-h
reviewed
Oct 20, 2024
| throw new ArgumentException("Failed to resolve given dns endpoint.", nameof(endPoint)); | ||
| } | ||
|
|
||
| endPoint = new IPEndPoint(resolved[0], dnsEndPoint.Port); |
There was a problem hiding this comment.
Should we select random if it resolves to multiple hosts?
There was a problem hiding this comment.
I'm not really expecting UDP servers to live for long, so I don't care too much 🤣
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I changed Steam directory api to return DNS servers recently in #1422, and it works fine for TCP connections, but UDP connections throw that they can't send a packet to a DNS endpoint.
I also removed manual resolution of DNS for default server in #1452.