MC-232009Minecraft does not resolve SRV records correctly
Minecraft is unable to connect to multiplayer server that have ports in SRV DNS records set running on non-default (25565) port causing issues to servers on shared hostings.
Example server:
adv.glowingmines.eu (:27528)
After some testing it looks like the problem might be in some defaulting to IPv6 even though it is not present.
In Windows OS, when you go to the Adapter settings and disable the IPv6 protocol, Minecraft is able to correctly resolve the SRV record and connect to the server (see image_2021-07-13_23-42-16.jpg) (sorry it's in czech but hopefully you'll know what dialog window I mean 🙂)
However when the IPv6 protocol is enabled but the IPv6 on the network is not available, the SRV is not working.
During testing I tried changing the DNS server to 1.1.1.1, 8.8.8.8 and CZ.NIC ODVR
193.17.47.1 however the used DNS server did not affect the testing.
There are some users using different internet provider who don't seem to be having the same issue with this DNS setting and can connect correctly.
This issue does not affect those servers running on Minecraft default port 25565.
Environment
Windows 10 21H1
Minecraft 1.17.1, Bundled Java 16 (issue persists on AdoptOpenJDK HotSpot 16)
Attachments1
NormalCreated Issue:
Minecraft does not resolve SRV records correctly
Minecraft is unable to connect to multiplayer server that have ports in SRV DNS records set running on non-default (25565) port causing issues to servers on shared hostings.
Example server:
adv.glowingmines.eu (:27528)After some testing it looks like the problem might be in some defaulting to IPv6 even though it is not present.
In Windows OS, when you go to the Adapter settings and disable the IPv6 protocol, Minecraft is able to correctly resolve the SRV record and connect to the server (see image_2021-07-13_23-42-16.jpg) (sorry it's in czech but hopefully you'll know what dialog window I mean 🙂)However when the IPv6 protocol is enabled but the IPv6 on the network is not available, the SRV is not working.
During testing I tried changing the DNS server to 1.1.1.1, 8.8.8.8 and CZ.NIC ODVR
193.17.47.1 however the used DNS server did not affect the testing.There are some users using different internet provider who don't seem to be having the same issue with this DNS setting and can connect correctly.
This issue does not affect those servers running on Minecraft default port 25565.
Environment
Windows 10 21H1
Minecraft 1.17.1, Bundled Java 16 (issue persists on AdoptOpenJDK HotSpot 16)
Attachments1
![[Mojang] Adrian Östergård](../../../data/assets/gravatar/nighter.jpeg){kind=small}
![[Bot] Arisa](../../../data/avatars/users/43007.png){kind=small}
![[Mod] ampolive](../../../data/avatars/users/18949.svg){kind=small}
Hello, we've invested a bit of time in this and come to the conclusion that we won't be supporting IPv6 in the foreseeable future. We have balanced being backward compatible with older operating systems, the time needed to validate that the new protocol works, as well as the benefits that this gives.
Minecraft is still seeing IPv6 issues (see MC-232009 and JDK-8272996). Until we reach a point where all our games, launchers, dependencies and supported operating systems fully work with IPv6 we won't be turning it on for any of our endpoints. For the time being, we won't be fixing this.
Hello, we've invested a bit of time in this and come to the conclusion that we won't be supporting IPv6 in the foreseeable future. We have balanced being backward compatible with older operating systems, the time needed to validate that the new protocol works, as well as the benefits that this gives.
Minecraft is still seeing IPv6 issues (see MC-232009 and JDK-8272996). Until we reach a point where all our games, launchers, dependencies and supported operating systems fully work with IPv6 we won't be turning it on for any of our endpoints. For the time being, we won't be fixing this.
Hello, we've invested a bit of time in this and come to the conclusion that we won't be supporting IPv6 in the foreseeable future. We have balanced being backward compatible with older operating systems, the time needed to validate that the new protocol works, as well as the benefits that this gives.
Minecraft is still seeing IPv6 issues (see MC-232009 and JDK-8272996). Until we reach a point where all our games, launchers, dependencies and supported operating systems fully work with IPv6 we won't be turning it on for any of our endpoints. For the time being, we won't be fixing this.
![[Mod] Asteraoth](../../../data/avatars/users/92886.png){kind=small}
Thank you for your report!
However, this issue is Invalid.
Your Minecraft version is outdated. We currently take issues for version 1.19.2 and the latest snapshot.
Please update to the latest version as it includes the newest fixes. If you still have this problem after updating, then please create a new issue.
In case of a game crash, please also attach the crash report found in minecraft/crash-reports/crash-<DATE>-client.txt.
Does using version 22w18a (1.19) and above solve your issue? If so, your issue would be MC-232009.
Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki
Same issue here, only disabling IPv6 helped, almost every normal user is not able to do such a complicated thing, we have that issue since Minecraft 1.17
Please Mojang, we really hope this gets fixed in 1.18, an update from the Mojang Team on that would be great!
I am having the same problem. Please get this fixed!! This is the error:
Failed to connect to the server
io.netty.channel.AbstractChannel$AnnotatedConnectException: Connection timed out:
no further information: [IP Address]:25565
It tells you in the error message that it is just ignoring the SRV record and using the default port.
SRV record is ignored if IPv6 is enabled.
In my case I have ipv6 with correct address and ipv6 inet working. MC with SRV record is on ipv4 and as mentioned - in this scenario it is ignored. (since version 1.17.1 - in 1.17 or older, SRV record work correctly)
This also happens with MacOS Big Sur (11.6.1). Adding "-Djava.net.preferIPv4Stack=true" to the JVM args did not help.
The issue still persists on Minecraft 1.18.1, can @Mojang PLEASE fix this, we are getting more and more users that cannot join our servers anymore..
Is this still an issue on 1.18.2?
Yes it's still an issue in 1.18.2
As a clarification: this is a JVM issue. Fix is available in latest JDK release 17.0.2, but we still need to update version available in launcher.
Is there any date known, when the Java version on the launcher gets updated?
Can we expect that this/next month?
Finally! I complained about this in
MC-228162and was just shutdown instantly a while ago just to see it actually get looked into now.. omg ty