The reason why the new address works on some players but not on others may be due to the old DNS result remaining in the cache. First compare the authorized record and the externally visible record.
Step by step
-
Verify in the DNS panel that the change was made to the correct subdomain. If you're using SRV, check both the SRV record and its destination.
-
Query A, AAAA and the corresponding SRV record with two different analyzers. If the results are splitting, first examine the TTL value and name servers of the old record.
-
If there are any old local results left on your Windows device, query again after
ipconfig /flushdns. This command does not clear the cache of other players or providers. -
When the same destination and port appear from two networks, try the real Minecraft connection again.
Keep in mind
During address migration, take into account that some players may go to the old server during the previous TTL period.