Re: Long failover time...

Thanks and I appretiate your reply...

Is it required to create a PTR record for the Cluster Name in the DNS
Server??? We already have a cluster whose name is registered in the DNS only
for forward lookup...

Thanks.
Arun M

"John Fullbright" wrote:

"The server for 143.3.16.172.in-addr.arpa. could not be contacted over
adapter
'Public' to determine whether it accepts DNS registration updates. Retrying
at a later time"

Looks like problems contacting an authoratative DNS server for the reverse
lookup zone that holds the PTR record.

..

"LOVEBEINGDBA" <LOVEBEINGDBA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A70ABBFB-6DDA-495D-B715-542869DC021C@xxxxxxxxxxxxxxxx
Environment:
Windows Server 2003 R2 x64 SP2
MSCS 2 node failover cluster

Failover takes about 2 minutes. When doing the failover the clustername
take
a long time to come back up.

Clustername has been registered in the DNS for forward look up .

We have another production cluster and that works fine in the same setup.

These are the lines I found that are related to this issue from cluster
log:

00000840.00000bb4::2007/08/06-16:57:27.835 WARN Network Name <Cluster
Name>:
The server for 143.3.16.172.in-addr.arpa. could not be contacted over
adapter
'Public' to determine whether it accepts DNS registration updates.
Retrying
at a later time.
00000840.00000bb4::2007/08/06-16:57:27.835 INFO Network Name <Cluster
Name>:
Replaced DNS name <clustername.domain> with IP Address 172.16.3.143 over
adapter 'Public'.
00000840.00000b08::2007/08/06-16:57:28.679 INFO Network Name: time until
next DNS reg: 2007/08/06-22:17:35 (128309122556769715)
00000840.00000bb4::2007/08/06-16:58:26.795 WARN Network Name <Cluster
Name>:
Failed to register DNS PTR record 143.3.16.172.in-addr.arpa. for host
<clustername.domain> over adapter 'Public', status 1460
00000840.00000bb4::2007/08/06-16:58:26.795 INFO Network Name <Cluster
Name>:
Modified DNS name <clustername.domain> with IP Address 172.16.3.143 over
adapter 'Public'.
00000840.00000b08::2007/08/06-16:58:28.638 INFO Network Name: time until
next DNS reg: 2007/08/06-22:17:35 (128309122556769715)

Any help will be greatly appretiated.



.

Relevant Pages

  • Re: issue with DC replication
    ... Are the addresses in the same network ID as the FTP servers? ... different AD-I DNS server ip address which will provide the DNS services. ... Well, if it fails when DC1 is down, that means that for some reason DC2 is not responding to the server requests when DC1 is down (also check if both ... >> have 2 DCs that are supporting that cluster? ...
    (microsoft.public.windows.server.active_directory)
  • Re: issue with DC replication
    ... different AD-I DNS server ip address which will provide the DNS services. ... I think that when you lose resolution between the FTP and the DNS/DC ... You have one FTP cluster in Active/Passive configuration? ...
    (microsoft.public.windows.server.active_directory)
  • Re: Exchange install failed
    ... Not knowing anything about your DNS topology, it is hard to say if you need to do that or not. ... Please do not send email directly to this alias. ... I will change the DNS entries on the server to point to ... In fact the cluster itself passed all readiness ...
    (microsoft.public.exchange.setup)
  • Re: Slow Cluster share
    ... You might be having a DNS issue as in bullet 5: ... If the Windows 2000 or Windows Server 2003clusternodes are the only domain ... Both members of theclusterare domain controllers. ... If I were to take the cluster out of being DCs and set up other DCs ...
    (microsoft.public.windows.server.clustering)
  • Re: issue with DC replication
    ... DNS AD-I running on 217.54.46.0 subnet..Some routing mechnism is ... different AD-I DNS server ip address which will provide the DNS services. ... I think that when you lose resolution between the FTP and the DNS/DC ... You have one FTP cluster in Active/Passive configuration? ...
    (microsoft.public.windows.server.active_directory)
Loading