You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The client performs by default a DNS resolution when only one server address is provided. This is to enable DNS-based load-balancing, see #138. As stated in #138 (comment) it makes TLS hostname verification fail, because the hostname of the server certificate isn't likely to match the IP resolved by the DNS query.
For 4.x and 5.x, the client shouldn't use DNS resolution as soon as TLS is enabled. This would at least avoid making TLS troubleshooting even more difficult.
DNS resolution would then need to be explicitly set up as of 6.0.0.
The client performs by default a DNS resolution when only one server address is provided. This is to enable DNS-based load-balancing, see #138. As stated in #138 (comment) it makes TLS hostname verification fail, because the hostname of the server certificate isn't likely to match the IP resolved by the DNS query.
For 4.x and 5.x, the client shouldn't use DNS resolution as soon as TLS is enabled. This would at least avoid making TLS troubleshooting even more difficult.
DNS resolution would then need to be explicitly set up as of 6.0.0.
References #138, #394.
The text was updated successfully, but these errors were encountered: