Connection DNS resolution and SSL validation after DBeaver 23.3 per-connection truststore change
DBeaver delegates DNS lookups to the underlying JVM, which caches results according to the networkaddress.cache.ttl system property. The UI does not expose a runtime control to invalidate that cache for a specific connection. Starting with DBeaver 23.3, a per-connection property useCustomTruststore allows distinct truststores per connection. The connection w
dbeaver