Virtual hosts doesn't seem to support SRV about serverlistplus

[stephan-gh]

Are you using the Bukkit or the BungeeCord version? If you're on Bukkit, make sure to install ProtocolLib. Otherwise it should work, although I'm going to verify this for the newer versions.

[frdmn]

@Minecrell I'm using the latest Spigot/Bukkit version (ServerListPlusUniversal_3.3.2.jar). I also made sure the latest verison of ProtocolLib is installed (ProtocolLib_3.6.3b75.jar from Jenkins).

[frdmn]

Is this resolved now?

[stephan-gh]

It should, I've tested it before releasing the new version (3.4). If it is still not working, write here again then I can take a look again.

[frdmn]

Thanks, I'll report back as soon as I tried said version 👍

[frdmn]

@Minecrell Just tried the latest release from GitHub releases. Still no luck:

My server connections:

---

[stephan-gh]

I don't know exactly but let me guess: SRV records get resolved on the client. Then, it simply connects with the IP that's in there. It is probably sending the resolved SRV address to the server, so there is no way to get the original SRV hostname used in the Minecraft client. For this SRV record, it is simply always sending obi-wan.yeahwh.at:25575 to the server instead of frd.mn as you would expect.

You can define a special hostname in the SRV record to be still able to detect this SRV record.

Note: Not completely sure about this, would need to check first to make sure this is the reason.

[frdmn]

@Minecrell You are right, when I try this in the configuration:

Hosts:
  obi-wan.yeahwh.at:
    Default:
      Description:
      - |-
        &a&lYEAHWHAT?!&r&6 Minecraft server.
        &6Still using &4&lfrd.mn&6, eh?
    Personalized:
      Description:
      - |-
        &6Welcome back to &a&lYEAHWHAT?!&r&6, &c%player%&6!
        &6Still using &4&lfrd.mn&6, eh?

... I see said description, but I am not sure if that's the "purposed" behaviour.

ideas?

[stephan-gh]

It might not be directly the purposed behaviour of ServerListPlus, but from the server-side you can do nothing against it. The server depends completely on the information provided by the client, so if the client resolves the SRV record and then sends the resolved address instead of the original one there is no way for the server to figure out the original hostname as entered by the user.

You will need to define a special hostname for the SRV record so you will be still able to detect users using it, unfortunately I doubt there is another way around this. Sorry!