Recently noticed that my SRV records are not working, nothing has changed from what i can think of for this to now stop. Basically we have SRV records to point from {Server}.brierie.net to {Server}.brierie.access.ly which was working fine but now no one can connect.
Checked the hostname which the SRV points too and can connect fine through that but not through brierie.net.
Anything you can do to help with this, i did see there was something prevously on may that there was an issue with this?
Thanks for responding, i have pointed this to the IP address we use for the servers, but even with this pointed it still doesnt seem to be working for the SRV record.
So ive made sure that lobby.brierie.access.ly is pointed to the correct IP which it is. I have then looked at cloudflares settings for the A record which is brierie.net pointing to the same IP. I have checked the SRV record which is lobby for the name which points to lobby.brierie.access.ly
Even when i ping on my computer it says the below:
Pinging brierie.net [178.32.171.0] with 32 bytes of data:
Reply from 178.32.171.0: bytes=32 time=19ms TTL=52
Reply from 178.32.171.0: bytes=32 time=18ms TTL=52
Reply from 178.32.171.0: bytes=32 time=18ms TTL=52
Reply from 178.32.171.0: bytes=32 time=18ms TTL=52
Ping statistics for 178.32.171.0:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 19ms, Average = 18ms
C:\Users\brier>ping lobby.brierie.access.ly
Pinging lobby.brierie.access.ly [178.32.171.0] with 32 bytes of data:
Reply from 178.32.171.0: bytes=32 time=18ms TTL=52
Reply from 178.32.171.0: bytes=32 time=18ms TTL=52
Reply from 178.32.171.0: bytes=32 time=18ms TTL=52
Reply from 178.32.171.0: bytes=32 time=17ms TTL=52
Ping statistics for 178.32.171.0:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 18ms, Average = 17ms
Not sure what i am doing wrong here, basically we used to have it set up where people would use the hostname lobby.brierie.net when using this it then ported through the other hostname lobby.brierie.access.ly and worked fine but now its not working at all.
There’s most likely no CNAME or “A” record called “lobby” in your DNS page here. I do believe that’s required, in addition to the SRV record.
This was supposedly an issue in the last ticket about this issue with minecraft and srv records.
Is there a way to resolve this going forward as i really need this to work for players to be able to connect with our hold original hostname.
@TKlein
Hi there, This is related to a bug we had last night. It’s already fixed but some zones are still experiencing in issue with it. In this case, we need to force the zone to be rebuild. For this, please tag me (@tklein) with the name of your zone or alternatively, if you don’t want your zone name to…
HI @domjh Yes the SRV points to an external hostname which is brierie.access.ly this is something we have done for a few years now with no issues. but now it doesnt seem to be working. What i can confirm is that if i just direct connect using brierie.access.ly that will work so it seems to be an issue with the SRV/Cloudflare not too sure what i can do to then resolve this issue.
I’m not really too sure what the issue could be. Cloudflare doesn’t proxy non HTTP traffic and the record is not pointing to a Cloudflare hostname.
I brought up the client and before that also flushed my DNS chache but when trying to connect i get this:
Connecting to lobby.brierie.net, 25565
16:06:31.383
Couldn’t connect to server
java.net.UnknownHostException: lobby.brierie.net
at java.net.InetAddress.getAllByName0(InetAddress.java:1280)
at java.net.InetAddress.getAllByName(InetAddress.java:1192)
at java.net.InetAddress.getAllByName(InetAddress.java:1126)
at java.net.InetAddress.getByName(InetAddress.java:1076)
at net.minecraft.client.multiplayer.GuiConnecting$1.run(GuiConnecting.java:67)
I’m pretty sure it shouldn’t be needed, but can you try adding an A record for lobby pointing to the Minecraft server IP?
I’m not sure what the error formatting is in the MC client, but it appears to be trying to connect to port 25565 on your lobby hostname, rather than the one specified in the SRV target.
I can give it a try but the only issue with that i think is then it will go direct to the A record and not use the SRV which is what i am wanting it to do basically, im not all too well versed in DNS systems XD
