Change "primary" IP of cluster member

[ITsmyfault]

Hi -

Win2K cluster is up and running. Odd problem seems to be related to DNS.. the machine keeps using the heartbeat IP as it's "primary" address. By that I mean if you ping "servername" it responds with "server.domain.com 10.0.0.1" as opposed to it's "real" IP on the LAN. Other apps are having trouble with this as well; Arcserve won't autodetect clients to backup bc it is also scanning the 10.0.0.0 network. There must be a reversed reg key somewhere. Anyone fixed this before? DNS has both entries, but is only using the "wrong" one. I tried deleting it but no joy.. My other cluster does not have this problem and i built them the same way (actually I followed a checklist so I would not have issues like this.. so much for the best laid plans!)
Thx - Joe

 

[acunning]

The only thing I can think of is that somehow the private/public network configuration has got mixed up. Have you checked this in Cluster Administrator?

 

[ITsmyfault]

I did, thx. It was fine.

What I wound up doing was a little drastic but it worked..
I uninstalled clustering.
Then I uninstalled AD & DNS.
Then I disabled the other nics, leaving only a single LAN nic.
Then reinstalled DNS and checked the records for the host.
Now it acts properly..
There is probably a better way, but this worked.
thx!

 

[flaurijssens]

Make sure that 'Register this connection's addresses in DNS' is unchecked. This setting is in the properties of the heartbeat NIC, TCP/IP properties, advanced, DNS tab.