Thin JDBC driver may have FQDN (host name) at a connection string.
Currently, it resolves this FQDN to one IP and tries to connect to this IP only.
It is better to try to connect to multiple IPs one-by-one if DNS returns multiple A-records (FQDN can be resolved to several IPs) until successful connection. It could give a simple fallback option for the JDBC thin driver users.
A similar functionality is already implemented in ODBC driver.