Lazar Bodor

Same for me on 2.2.0.

Thanks for getting back to me. Here is how I connect. ``` EventStoreDBClient.create( EventStoreDBClientSettings.builder() .dnsDiscover(true) .addHost(hostname, 443) .tls(true) .buildConnectionSettings() ); ``` Since DNS discovery is true and `hostname` resolves to...

``` $ host nodes.dev-xxx nodes.dev-xxx has address 13.55.106.44 nodes.dev-xxx has address 3.104.208.149 nodes.dev-xxx has address 52.64.13.213 ``` Node 13.55.106.44 is down, others are up. The issue is present when DNS...

Hi @YoEight, does the above log show what you wanted to see? Are you able to reproduce the problem?

I _think_ that our DNS setup is pretty standard, provided by AWS Route53. Here it is as shown by `aws route53 list-list-resource-record-sets` ``` ... { "Name": "nodes.dev-xxx.", "Type": "A", "SetIdentifier":...

OK, thanks. I'll send you the details shortly via DM on discord to keep the DNS name private.

On second thought, I made a temporary DNS multiaddress A record, which I can share here. ``` $ host es-tmp-1.geodesy.ga.gov.au es-tmp-1.geodesy.ga.gov.au has address 3.24.251.198 es-tmp-1.geodesy.ga.gov.au has address 3.105.10.86 es-tmp-1.geodesy.ga.gov.au has...

You don't need a cluster to reproduce the issue. All you need is a DNS record that resolves to 3 IP addresses. The issue is that the Java client doesn't...

From https://developers.eventstore.com/server/v24.6/cluster.html#cluster-with-dns: ``` When you tell EventStoreDB to use DNS for its gossip, the server will resolve the DNS name to a list of IP addresses and connect to each...

That would be great. Thanks very much.