Ok so I’ve read all 10 or so topics regarding the configuration of srv records here on digital ocean but they’re all seem outdated.

I’m trying to setup an srv record for a minecraft server.

I know how to set them up since I’ve had this minecraft server for a while and and the srv record was working just fine on my previous host provider but I can’t seem to get it to work with digital ocean.

Here’s the previous working configuration I had and that it shows up on most srv configuration tutorials on google:

an A Record pointing to server’s ip (minecraft server) example:
mc.example.com

and the SRV pointing to that same A Record as such:

Host: minecraft.tcp.play
Points to: mc.example.com.
port: 10041code
Priority: 0
Weight: 5

Should be accessible through play.example.com

That seems logical and it works, but not on Digital Ocean, here is what I get when I try those same settings:

https://image.prntscr.com/image/UpAu6gZkTW_NzQ4MKLVi8A.png

apparenty for some odd reason it won’t take the already known to work minecraft.tcp.play
but it will take minecraft.tcp (without an specified subdomain)
as seen on the next screenshot:

https://image.prntscr.com/image/KvW5gv1YT2y9784RM7abAg.png

Then, I thougt, maybe in this new Digital Ocean Interface I don’t need to specify the subdomain directly into the hostname and all I have to do is point it to the A record, so I tried:

https://image.prntscr.com/image/8sTknKXgTf6NOFNR4bIcuw.png

Digital Ocean seems to take that configuration but it just won’t work.

The play.mydomain.com is reachable since it does exists as an A record but the srv configuration just won’t kick in.

I’ve tried every single possible combination to no avail.

Anyone knows how to get an srv record working on the most recent Digital Ocean’s interface?