Add retry or IP validation when cluster slots has one node IP address is 0@0

[SaiSasankKhajjayam]

Hi ,

we are using this library for a while now and encountered one strange issue. In Our redis cluster holds 13 primaries and 2 slaves each and total of 39 redis pods in the system.
One of the slave node has bad cluster node view like below where master node has noaddr tag and IP assigned to 0.
==================================Bad Node View=====================
92.168.142.191:6379: 0d7bb6c0fd8f5bdd546716ac7058449a8df17ab4 192.168.142.158:6379@16379 slave b1d860c3242fa36002afe1612d5fa59dbcabd42c 0 1736470239533 49 connected​
421a2663b9fda621c3131644bfa96cf15d2738d8 192.168.72.237:6379@16379 master - 0 1736470239000 2 connected 0-1260​
d5f25ca9b4e0bcfa7e2f0a6e80e2fc2d7bbb35a0 192.168.21.177:6379@16379 master - 0 1736470240540 48 connected 10088-11348​
b1d860c3242fa36002afe1612d5fa59dbcabd42c 192.168.7.224:6379@16379 master - 0 1736470239000 49 connected 8827-10087​
3a706ea9cda7b8e6f67024530972e8579fa70eb8 192.168.82.164:6379@16379 master - 0 1736470238526 52 connected 3783-5043​
a28f27471882538caf854833e7dc2d71825a377f 192.168.183.36:6379@16379 master - 0 1736470239000 50 connected 15132-16383​
e2d20b7f10b2d9cd488d2703e2b072586d74db2d 192.168.189.154:6379@16379 master - 0 1736470240000 38 connected 12610-13870​
a7ff986e82e578fc1d3d76d17770a26d278fb3fe 192.168.230.150:6379@16379 master - 0 1736470240137 46 connected 6305-7565​
c1cf6355456ea4f81d5aecdc26a3e17f4df72199 192.168.206.241:6379@16379 master - 0 1736470239000 54 connected 5044-6304​
b2b91d084a36016a6ac31ef986da5582335ecb1e 192.168.122.203:6379@16379 master - 0 1736470239000 37 connected 11349-12609​
8f3b1dabf05499eebc950108705fb9865f1509c4 192.168.237.254:6379@16379 master - 0 1736470239533 41 connected​
ffd5df303719bb538c46ca429ff3ee5197126c9b :0@0 master,noaddr - 1736470240540 1736470240000 43 disconnected 2522-3782 7566-8826​
e08d731c49626fa026e870465d51a7b4a9f570be 192.168.244.166:6379@16379 master - 0 1736470239000 39 connected 13871-15131​
5707a8358cf1c999a453220ba1a9acb121e419d1 192.168.22.190:6379@16379 master - 0 1736470240137 44 connected 1261-2521

====================================================================================
cluster is accessed through DNS so cluster slots commands fetched by library can land on any of node. when cluster slots command lands on this bad node its assuming 0@0 is one of master IP. we are seeing below tcp error.

error: dial tcp :0: connect: connection refused

can we add some validations to ip's when cluster slots info fetched?

​