Re: Public adapter configuration

From: Ramon Jiménez (rjimenezm.athome_at_my.hotmail.com)
Date: 08/21/04


Date: Sat, 21 Aug 2004 23:39:54 +0200

Sure... I was wrong regarding the DNS.. I misunderstood somehow the
question...

Regading IP registration for the private NIC...it is done by the Netlogon
service, not by the NIC itself...

The Host's "A" Record Is Registered in DNS After You Choose Not to Register
the Connection's Address
http://support.microsoft.com/default.aspx?kbid=275554

How to Prevent Domain Controllers from Dynamically Registering DNS Names
http://support.microsoft.com/default.aspx?scid=kb;en-us;198767

-- 
Saludos
Ramon
PMP, ITIL Certified
MCSE & MCSA 2000/2003, CCA
"taylor" <taylor@discussions.microsoft.com> wrote in message 
news:a84301c487c5$03af3e60$a401280a@phx.gbl...
>I have solved the first issue, it was an error in the
> Cluster IP address configuration.
>
> For the DNS issue, MS KB 281662 article says that node 1
> points to node1 dns(primary) and to node 2 DNS(secondary,
> I hope this is right.
> The thing that i dont get in this article is the
> following "You must address the problem of the ability to
> not register the private interface in DNS, especially if
> it is connected by way of a crossover cable (two-node
> only)."
> hope If someone can lear this point out
>
> Thanx
>>-----Original Message-----
>>1.-
>>What IP's has Private Nic and Public Nic?
>>
>>It seems like you have used private NIC subnet to define
> any virtual IP
>>resource (that's why you get a dependency error when you
> try to make it
>>private only)
>>
>>2.-
>>DNS: Node 1 has to point to Node 2 and Node 2 to Node 1
> as primary and
>>themselves as secondary
>>
>>-- 
>>Saludos
>>Ramon
>>PMP, ITIL Certified
>>MCSE & MCSA 2000/2003, CCA
>>"taylor" <anonymous@discussions.microsoft.com> wrote in
> message
>>news:34bd01c487b7$46675ac0$a301280a@phx.gbl...
>>>
>>> I have just configured cluster service on Node1 of a2
> node
>>> cluster. The problem I'm facing is that the properties
> of
>>> the private cluster network indicates the private nic
> to
>>> be used for mixed mode, but when I try to make it only
>>> for private communication I get a dependency error.
>>>
>>> My second question concerns DNS. My two cluster nodes
> are
>>> DC and DNs servers pointing to themselves as primaary
> DNS
>>> servers.
>>> If there are no host(a) records for node2 on node1 DNS
>>> and viceversa shall I create them Manualy.
>>>
>>> Thanx
>>
>>
>>.
>> 


Relevant Pages

  • Re: Long failover time...
    ... the delays you are experiencing can be attributed to attempts to register in a reverse look-up zone that either does not exist or is not configured for dynamic updates. ... Is it mandatory to create PTR record for the ClusterName in the DNS Server? ... We already have a production cluster, whose name is registered in the DNS, ...
    (microsoft.public.windows.server.clustering)
  • Re: Public adapter configuration
    ... Cluster IP address configuration. ... For the DNS issue, MS KB 281662 article says that node 1 ... >What IP's has Private Nic and Public Nic? ... >> DC and DNs servers pointing to themselves as primaary ...
    (microsoft.public.windows.server.clustering)
  • Re: Errors 40960 & 40961 ...
    ... >> private workgroup. ... Servers in a workgroup running DNS. ... >> have reverse lookups for their records. ... Win2k3 and XP will try to register the PTR records for the ...
    (microsoft.public.windows.server.dns)
  • Re: Errors 40960 & 40961 ...
    ... Then Kevin replied below: ... > private workgroup. ... Servers in a workgroup running DNS. ... Win2k3 and XP will try to register the PTR records for the ...
    (microsoft.public.windows.server.dns)
  • Re: Long failover time...
    ... Create the "RegisterReverseLookup" as in the section "New and modified DNS ... Is it required to create a PTR record for the Cluster Name in the DNS ... Failed to register DNS PTR record 143.3.16.172.in-addr.arpa. ...
    (microsoft.public.windows.server.clustering)