Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
- From: "Charles Law" <blank@xxxxxxxxxxx>
- Date: Tue, 18 Dec 2007 22:32:35 -0000
Hi Russ
Thanks for the reply.
Can you right click the cluster group and move it to Server2 and then back
again to Server1?
Yes, I can. So now I think I only have one problem: the multiple DNS thing
(not withstanding, the nightmare configuration).
This is a very bad idea. You should never cluster domain controllers.
I'm not disagreeing, but more than one Microsoft document says that this is
ok. I saw a reference in another thread you are helping in, and the
Microsoft guide I have been following also makes reference to this as a
viable configuration.
What I need to know is, can it work, and/or can it be made to work? What, in
practice, are going to be my problems?
In the meantime, Server1 failed to register its IP info on the DNS in
Server2 and thus registered with itself only.
I know not ideal, but isn't that the point of each server pointing to each
other for DNS resolution?
Just for the moment, if I could get this DNS issue resolved, then I would be
happier. Do you know why I get the message, and what would put it right?
Cheers.
Charles
"Russ Kaufmann [MVP]" <russ@xxxxxxxxxxxxxxx> wrote in message
news:C902086F-D3FD-4345-9DF7-69782E386514@xxxxxxxxxxxxxxxx
"Charles Law" <blank@xxxxxxxxxxx> wrote in message
news:ubUMpAaQIHA.5980@xxxxxxxxxxxxxxxxxxxxxxx
MyServer1 is a domain controller, and so is MyServer2, as recommended in
the MS guide. Both have DNS installed.
This is a very bad idea. You should never cluster domain controllers.
I have configured and checked a private and public network between the
servers; the private network is over a short cross-over cable, whilst the
public network goes to an unmanaged Gigabit switch. I have fixed IP
addresses all round, and can ping everything in sight. The server's
public network configurations point to each other for primary DNS and to
themselves for secondary DNS. The private network has only TCP/IP
enabled, no default gateway or DNS, no LMHOSTS, and NetBIOS disabled.
DNS should be on a remote DNS server. This is especially true when doing
what you are doing.
The first odd thing to note is that when I try to add node 2, it is
unable to see drives Q: through S:. That is, I start node 1, wait a while
and then start server 2.
In the meantime, Server1 failed to register its IP info on the DNS in
Server2 and thus registered with itself only.
If I look in Computer Management | Disk Management, the three disks have
'no entry' signs on them, and are marked as unreadable.
This is expected behaviour as Server1 owns the disks.
If I keep clicking Next when adding the second node, the wizard completes
and tells me that node 2 was added successfully, but I don't believe it.
If I open Cluster Administrator I can see two nodes: MyServer1 and
MyServer2. MyServer1, Active Resources contains entries for
Cluster IP Address
Cluster Name
Disk Q
Disk R
Disk S
Sounds to me like you have a cluster.
MyServer2, Active Resources is empty, as is the Active Groups folder in
Cluster Administrator.
Yep, because they are all active on Server1.
Can anyone tell me what I could have done wrong, or how I can home in on
the cause of this problem? It looks like there could be more than one
problem: a) the multiple DNS issue, and b) the inability to read the
quorum disk on server 2 when node 1 is on.
Can you right click the cluster group and move it to Server2 and then back
again to Server1? If yes, then you are done. You ahve a cluster. A cluster
that is configured like a nightmare, but a still a cluster.
--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp
The next ClusterHelp classes are:
Jan 18 - 31 in Denver
Mar 10- 13 in Denver
.
- Follow-Ups:
- Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
- From: Russ Kaufmann [MVP]
- Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
- References:
- Prev by Date: Re: Automatic Windows Updates Cause Failover But Resources Don't Start
- Next by Date: Re: Building 2-node WIN2K3 Cluster
- Previous by thread: Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
- Next by thread: Re: Cannot Add Second Node to Cluster: Multiple DNS records were found for "MyServer.MyNet.local"
- Index(es):
Relevant Pages
|