Add DNS SRV record resolution to client direct connection#16084
Add DNS SRV record resolution to client direct connection#16084Reidond wants to merge 2 commits intoFakeFishGames:masterfrom
Conversation
…nt to utilize it - Implemented DnsSrvResolver class for resolving SRV records using DnsClient. - Enhanced LidgrenEndpoint to perform SRV lookups when no port is specified. - Added unit tests for DnsSrvResolver to verify functionality.
I'm having a hard time imagining that. People don't normally go out of their way to make simple things such as joining a multiplayer game harder by randomly changing network addresses. Less than 10% of Barotrauma servers are dedicated, most just use Steamworks or whatever it is Epic uses, so this feature is for a niche of the niche. Or is this something that you would specifically use? Do you have one IP address where you want to host 10 Barotrauma servers, and need the links to be pretty too? |
There are many reasons to implement this:
|
|
@mygamingaccount |
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: