Problem with multihomed 2-node w2003 DC
JarnoMM
replies.
I'm having a problem with 2-node Windows 2003 cluster DC. Cluster is
running clustered sql server . Cluster configuration is made like Microsoft
recommends it in KB articles. However there's problem in DNS that occurs
after fail-over is performed to the cluster. Basic ip-addr setup is like
this:
MyClusterName 192.168.2. 10
MyClusterNode1 192.168.2. 11
MyClusterNode2 192.168.2. 12
MySqlClusterName 192.168.2. 13
First of all, how DNS registration should actually work in win2003 cluster?
Currently there are following entries registered into both nodes DNS's like
this when Node1 is active.
MyClusterName 192.168.2. 10
MyClusterNode1 192.168.2. 11
MyClusterNode1 192.168.2. 10 <- Should this entry be here?
MyClusterNode2 192.168.2. 12
MySqlClusterName 192.168.2. 13
MyClusterNode1Interconnect 10.1.1.1
MyClusterNode1Interconnect 10.1.1.2
- This works, but is it ok that 192.168.2.10 is registered as both
MyClusterName and MyClusterNode1 ?
All is working fine, until i move cluster to Node2. In this situation, it
gets messy as DNS has following entries soon in both nodes DNS:
MyClusterName 192.168.2. 10
MyClusterNode1 192.168.2. 10
MyClusterNode1 192.168.2. 11
MyClusterNode2 192.168.2. 12
MyClusterNode2 192.168.2. 10
MySqlClusterName 192.168.2. 13
MyClusterNode1Interconnect 10.1.1.1
MyClusterNode1Interconnect 10.1.1.2
So, de-registration doesn't occur for "MyClusterNode1 192.168.2. 10" and
nslookup gives incorrect IP 192.168.2. 10 for Node1. This then leads for
example to kerberos problems when Active Node2 tries to authenticate to
passive Node1.
So far, i've tried clear DNS manually and let system re-register all IP.
Tried also uncheck "Register this connection's address in DNS" but they still
registered cluster nodes like described above? Should i disable dns
registration totally like described in http://support.microsoft.com/kb/246804
?
Meinolf Weber
Check the Dependencies for Clusternode1, is it set to the ip from clusternode1
or the ip from clustername?
For the heartbeat set this configuration to get out the DNS entries:
-Clear all options except Internet Protocol TCP/IP
-On the DNS tab, verify that no values are defined. Make sure that the Register
this connection's addresses in DNS and Use this connection's DNS suffix in
DNS registration check boxes are cleared.
-On the WINS tab, verify that there are no values defined. Click Disable
NetBIOS over TCP/IP as shown in Figure 6 on the next page.
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> MyClusterNode2 192.168.2. 10
>
Meinolf Weber
Additional i suggest that you post here:
microsoft.public.windows.server.clustering
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
> Hello, I've posted this question previously to Cluster newsgroup but
JarnoMM
JarnoMM
you suggest below.
I didn't quite understand this: "Check the Dependencies for Clusternode1, is
it set to the ip from clusternode1 or the ip from clustername? "
There are "Cluster name" and "Cluster ip" resources in cluster and "Cluster
name" of course depends on cluster IP. Did you mean something else?
Meinolf Weber
open the properties and there you have a tab dependencies.
JarnoMM
"open the properties and there you have a tab dependencies."
If you mean dependencies between cluster resources in cluster administrator
tool, these are correctly set. There is "CLuster IP address resource" and
"Cluster name"-resource and name depends on IP. IP-resource is correctly
parametrized. I doubt that cluster could work at all if these would not be
ok.