Raphael Schweizer

Additional complexity for bonus points: (part of) the cluster might be hidden behind a proxy / load balancer requiring SNI, i.e. all (some) hostnames resolve to the same IP.

I got a response from the team providing "redis as a service"... the summary is as follows: > The advertised hosts when receiving a MOVED response are correct [...] >...

Yes, [`CLUSTER SLOTS`](https://redis.io/docs/latest/commands/cluster-slots/) is returning the host names (together with _optional_, non-routable IP adresses), so seems to be the better choice: ``` 0 0 0 1 5460 2 0 redis-7c2b3133-0bf4-0.redis.example...

`ClusterRouting: {Default,IP,Host}` (or even 'only' respecting the preferred order) seems good. If, for any reason, hosts / IPs are not reachable, an option to `ForceX` or `XOnly` would prevent polluting...