Add DNS SRV record resolution to client direct connection #16084
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.
Hello Barotrauma team 😇
In this PR I've added support for resolving DNS SRV records when client tries to join via Direct Join and enters domain name like
barotrauma.example.com.Why this is needed? Imagine that your dedicated server is hosting game server with different port than default one (
27015) for example42069so users have to write thisbarotrauma.example.com:42069which is ugly.DNS SRV solves this and allows to host multiple servers under same domain name.
Here are some context about it: