If more than one matching SRV record is specified, the Minecraft client picks one at random and tries connecting. If this connection attempt fails, no other SRV record is tried.

This is not the correct implementation and very unfortunate when server administrators try to provide redundant server gateways (BungeeCord proxies).

Taken from the Wikipedia article on SRV records:

The priority field determines the precedence of use of the record's data. Clients always use the SRV record with the lowest-numbered priority value first, and fallback to other records of equal or higher value if the connection to the host fails.

If a service has multiple SRV records with the same priority value, clients use the weight field to determine which host to use. The weight value is relevant only in relation to other weight values for the service, and only among records with the same priority value.

More details and an example can be found here: https://en.wikipedia.org/wiki/SRV_record#Provisioning_for_high_service_availability

The current implementation of SRV records is quite useless, if it can't provide high availability.

I'd love to see this bug fix implemented.