By Valkoor
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?
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
Hi!
The first configuration is correct. Unfortunately it looks like the validation rules for the hostname part of an SRV record need to be updated. I’m letting the right team know about this so we can get it sorted out, but meanwhile you can add the record using the API.
The easiest way to do it would be to use the doctl CLI client. See this tutorial for instructions on how to install it and authenticate. Once you’ve authenticated, run the following command:
doctl compute domain records create eraclashmc.com --record-type SRV --record-data "mc" --record-name "_minecraft._tcp.play" --record-port 10041 --record-priority 1 --record-weight 5
Let me know if that works!
Since I couldn’t wait until this problem got resolved I had to leave Digital Ocean and ended up finding a better deal but for everyone else having the same issue, simply handle your dns through your domain provider or cloudflare, srv records work great on both, cloudflare, not so good for enjin though.
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
Full documentation for every DigitalOcean product.
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
Stay up to date by signing up for DigitalOcean’s Infrastructure as a Newsletter.
New accounts only. By submitting your email you agree to our Privacy Policy
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.