-
-
Notifications
You must be signed in to change notification settings - Fork 59
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
SRV records may not be routed correctly. #172
Labels
Comments
Great issue description. I'll look into it as soon as I have the time. |
solved the problem? |
Not yet, I'm trying to fit in some time to catch up with the backlog of tickets as soon as I have the time. I would also really appreciate some more active maintainers, but I'll probably need to write some more documentation until someone is brave enough to touch the code 😕 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
When using SRV records, the domain of the target is referenced.
As a result, routing does not work correctly.
To Reproduce
OS:
Ubuntu 22.04.2 LTS (ARM)
Infrared Version:
ghcr.io/haveachin/infrared:2.0.0-alpha.13
Docker compose:
Infrared Config:
server.yml
How do you trigger the bug/issue?:
mc1.example.com
. You will then be connected to192.0.2.2:25565
.Expected behavior
If you connect on
mc1.example.com
, you will be routed to192.0.2.1:25565
.Additional context
I have only checked this with the Java Edition; it is possible that the Bedrock Editon may behave similarly, but since the Bedrock Edition does not allow the use of SRV records, I don't think this will be an issue.
The text was updated successfully, but these errors were encountered: