Re: DNS is picking up the heart beat address of the 2nd cluster node
- From: "Ace Fekay [MVP]" <PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx>
- Date: Sun, 29 Jan 2006 14:29:28 -0500
In news:1138428109.449990.7180@xxxxxxxxxxxxxxxxxxxxxxxxxxxx,
Chris <c_k159@xxxxxxxxx> stated, which I commented on below:
> Chris
> Jan 27, 5:52 pm show options
>
> Newsgroups: microsoft.public.windows.server.clustering
> From: "Chris" <c_k...@xxxxxxxxx> - Find messages by this author
> Date: 27 Jan 2006 15:52:29 -0800
> Local: Fri, Jan 27 2006 5:52 pm
> Subject: DNS is picking up the heart beat address of the 2nd cluster
> node
> Reply | Reply to Author | Forward | Print | Individual Message | Show
> original | Remove | Report Abuse
>
> Hi my name is Chris. I have a problem dealing with an active/passive
> cluster. I have 2 nodes. They are both running Windows 2003
> Enterprise.
>
> They have 2 NIC's in each server. Both nodes are DC's and both run
> DNS. The problem I am having is that DNS is picking up the 2nd nodes
> heart beat address of 10.0.0.2. and also picking up the LAN NIC
> address
>
> of 100.254.230.6. I have made sure that in the NIC properties of the
> heart beat that "Resister with DNS" is unchecked. This is causing
> problems with replication of the DC's to this node. The 1st node in
> the cluster has a heart beat of 10.0.0.1. The 1st node has a LAN IP
> address of 10.254.230.5. DNS is only picking up this address. This one
> 10.254.230.5 is the active node. They are connected via cross over. I
> am really scratching my head. Please help!!
IN addition to Todd's post, and hope it helps, a DC/DNS server will auto
register itself, whether the checkbox to not register is unchecked. To stop
it requires a series of reg entries, but Todd's suggestions should help. If
they do not, I can post the steps to kill registration for the unwanted NIC.
Classically, this is has always been an issue with multihomed DCs and many
engineers usually recommend not to mutlihome them.
Just a personal note, honestly I've never seen the advantage of clustering
DCs, but rather application servers such as Exchange or SQL, etc. You can
create multiple DCs to insure fault tolerance for directory services, but
for Exchange, it's more critical to have 24/7 since you can't easily move
mailboxes if the box goes down, hence why clustering Exchange is a clear
advantage, but not DCs, if you see what I mean.
--
Ace
This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.
Having difficulty reading or finding responses to your post?
Instead of the website you're using, I suggest to use OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. This is a direct link to the Microsoft Public
Newsgroups. It is FREE and requires NO ISP's Usenet account. OEx allows you
to easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject.
Not sure how? It's easy:
How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164
Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Assimilation Imminent. Resistance is Futile.
Infinite Diversities in Infinite Combinations.
The only thing in life is change. Anything less is a blackhole consuming
unnecessary energy.
===========================
.
- Follow-Ups:
- References:
- Prev by Date: Re: Setting-up DNS for Active Directory Users without losing user data.
- Next by Date: Re: DNS for TRUST Creation
- Previous by thread: Re: DNS is picking up the heart beat address of the 2nd cluster node
- Next by thread: Re: DNS is picking up the heart beat address of the 2nd cluster node
- Index(es):
Relevant Pages
|
