I'm having an issue while accessing an NLB cluster from node that is part of the cluster.
Here is the scenario.
I have created a NLB clusters on IP 10.10.10.110\255.0.0.0 [Protocol: both with filtering Single Host] in unicast mode having three nodes
10.10.10.109\255.0.0.0 -> Priority 2
10.10.10.134\255.0.0.0 -> Priority 1
10.10.10.101\255.0.0.0 -> Priority 3
Now if i access the cluster [10.10.10.110] from any other node[forsay 10.10.10.105] it resolves 10.10.10.109 that is what is expected.
Now if i hit 10.10.10.110 from host 10.10.10.109 it resolves to 10.10.10.109 that is not what is expected from the cluster. Similarly, if i access it from host 10.10.10.101 it resolves 10.10.10.101 despite of the priority of cluster.
What i believe is that its a loopback since the NLB IP is also registered on the current node, it resolve itself instead of hitting a cluster.
As of the application design, application is to be hosted on nodes that are part of the cluster and will hitting NLB cluster ip. I want to resolve node based on the cluster priority and status.
Please suggest how we can resolve this situation.