Correctness of DNS records Minecraft server
Hello, I would like to know if I have correctly configured DNS records, for my website and minecraft server. Because the minecraft server in the server list has started to refresh more poorly. What I mean here is that it takes several clicks on the refresh button for the server to finally show up as active. Compared to other servers, these show up active all the time.
A lizardmc.pl 66.59.208.43 < minecraft server ip
A lizardmc.pl 213.32.10.205 < ip server website
AAAA dc 2001:41d0:301:5::29, created as a subpage to redirect from the address dc.lizardmc.pl to the discord invite link.
AAAA lizardmc.pl 2001:41d0:301:5::29 < website server ip
AAAA www 2001:41d0:301:5::29 < ip server website
SRV < domain connection to minecraft sever
My question is whether this is caused by the fact that my cloudflare plan is a free plan and in order for the server refresh to improve on the list of servers I should either purchase a plan such as PRO, or simply do not use cloudflare and use OVH as the domain is purchased there, I should add that minecraft hosting is set up in Germany, and my location is Poland
15 Replies
My question is whether this is caused by the fact that my cloudflare plan is a free plan and in order for the server refresh to improve on the list of servers I should either purchase a plan such as PRO, or simply do not use cloudflare and use OVH as the domain is purchased there, I should add that minecraft hosting is set up in Germany, and my location is PolandNo, if you set it up right Cloudflare isn't a factor at all other then simply serving DNS Your issue is your setup doesn't make much sense.
A lizardmc.pl 66.59.208.43 < minecraft server ip A lizardmc.pl 213.32.10.205 < ip server websiteWhat this does, in effect, is return both IPs and Clients will randomly pick one to try, and some may fallback to retrying the other. Also it doesn't work for non-http connections proxied at all normally, but Cloudflare is saving you here and creating virtual records to make it work
;_minecraft._tcp.lizardmc.pl. IN SRV ;; ANSWER SECTION: _minecraft._tcp.lizardmc.pl. 300 IN SRV 1 1 25566 _dc-srv.c5b55c49236c._minecraft._tcp.lizardmc.pl. ;_dc-srv.c5b55c49236c._minecraft._tcp.lizardmc.pl. IN A ;; ANSWER SECTION: _dc-srv.c5b55c49236c._minecraft._tcp.lizardmc.pl. 300 IN A 213.32.10.205 _dc-srv.c5b55c49236c._minecraft._tcp.lizardmc.pl. 300 IN A 66.59.208.43What you need to do is separate out your Minecraft IPs onto a subdomain like play.lizardmc.pl, so like
A play 66.59.208.43 Dns-only
and then update your srv record to point at play.lizardmc.pl, and you'll still be able to connect by just inputting the domain name, then it should work everytime if you wait a bit for dns propagation/local cache to expireSo I have replace:
A lizardmc.pl 66.59.208.43
to:
A mc 66.59.208.43
and in SRV in name set mc?
So that the SRV has no doubt which Type A to use
SRV should stay named the same so people can connect by just inputting your domain name, and then sure you can use
mc, and then change the target of the srv to mc.lizardmc.plWell yes, except that I would like players not to enter ip mc.lizardmc.pl in the server list, but just lizardmc.pl.
Correct, so keep the srv at your root
That's the power of srv records, minecraft clients will specifically look up the srv record. You input
lizardmc.pl, and Minecraft looks up _minecraft._tcp.lizardmc.pl, and then it'll follow the Target to resolve it into an IP it can connect viaIn that case, replace name with "@" and in target set mc.lizardmc.pl?
yes, unproxy the
mc record as wellmc also on @?
Because then I will be back to the starting point of having two ip different again
by the same name
I think I'm lost
No, keep
mc A record as named mcOkey
Just click Edit and change the proxy status though, won't work proxied
CF does some magic to make srv records kind of work proxied while still exposing the IP Address but it makes the virtual A records with messy names, IP is exposed eitherway, cleaner to just unproxy it
Correct?
yup
https://mcsrvstat.us/server/lizardmc.pl works too
It may take a bit for your local dns cache to expire (maybe an hour or so at max), but once it does it should work every time to refresh/connect now
Thank you very much for your help. I wish you a good day