I need your help sometime. I have created the following SRV record for forwarding the subdomain play.meinedomain.de to a Minecraft server with port 25577. The subdomain is resolved (I land on the server), but the port is not bound.
A corresponding A record for the resolution of the subdomain is also available.
Is the SRV record so correct? Maybe someone of you had the same problem and can tell me where the problem is.
The aim is to reach the Minecraft server by specifying the subdomain. However, the port should not have to be specified for this!
I'm not sure now, but I think that the port must always be specified with 25565, i.e. Standard minecraft port, so that no port specification is necessary after the domain.
As I said, I'm not sure about that.
The server runs on 25577, so I try to specify this via an SRV record. But that's right, the standard port is 25565.
Here you have to check how the respective host evaluates this data field. There's no standard for this, it depends on the technical implementation at the hoster. The entry should also read in my opinion
0 0 25577 play.domain.de.
The final point is probably supplemented by the input tool anyway if the forwarding to the target domain works.
However, it can also be that the host does not allow any port entry and ignores everything in front of the target domain. Then it doesn't work → ask the hoster's support.
Have you tried to leave out the 0?
According to the Wiki, the structure of such an entry is probably like this: https://de.wikipedia.org/...rce_Record
And you have a surface from your provider to edit that. Certain things are probably given by the provider or you want to include them in the date.
Should the 0 be the weighting? (Mentioned as "weight" on Wikipedia?) Preference is probably what is called "priority" on Wikipedia. If the weighting should be 0, this must also be declared / allowed by the provider who makes this interface available for editing.
Otherwise it can lead to problems if it only translates this 1: 1 into port and destination (according to Wikipedia). Then he would have somehow port 0 and 25577 and the client then spacks around when connecting.
Edit: Or what FordPerfect says - is even more specific. It can actually be that not even a port entry is allowed by the hoster.
Yes, the 0 is the weighting. The 10 in preference is the priority. I'll try to leave out the 0, thanks!
