Re: Long failover time...

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

It is not 'mandatory' to register cluster info in a reverse look-up zone. However, 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. To improve failover, you should configure a reverse look-up zone and allow dynamic registrations, or follow John's recommendation.

--
Chuck Timon, Jr.
Microsoft Corporation
Windows Server 2008 Readiness Team
This posting is provided 'AS IS" with no warranties, and confers no rights.

"LOVEBEINGDBA" <LOVEBEINGDBA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:0EBDBFEE-98FC-4DFE-8B46-7B9E575CA0E4@xxxxxxxxxxxxxxxx
Thanks for your reply...
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,
only for forward lookup...

I couldn't find any documentation stating that we need to create reverse
lookup in the DNS Server.

Thanks.

"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: 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)
  • Re: Long failover time...
    ... If you are not using dynamic DNS, uncheck 'Register this connection in DNS' on the physical NIC configs. ... We have another production cluster and that works fine in the same setup. ... could not be contacted over adapter ...
    (microsoft.public.windows.server.clustering)
  • Re: Question On Clustering - Urgent
    ... Active- Passive Two node cluster. ... Is it possible that node 2 will only register only the host name not it's IP ... DNS" it register's both IP address and host name. ...
    (microsoft.public.windows.server.clustering)
  • Re: Public adapter configuration
    ... Regading IP registration for the private NIC...it is done by the Netlogon ... The Host's "A" Record Is Registered in DNS After You Choose Not to Register ... >I have solved the first issue, it was an error in the> Cluster IP address configuration. ...
    (microsoft.public.windows.server.clustering)
  • Re: Does this error occur with clients using ISP DNS servers?
    ... > have a reverse look-up zone configured for my internal domain. ... If you have your ISP's DNS listed, yet it will cause the same error. ... trying to register in the ISP's DNS, which in turn sends the registration ...
    (microsoft.public.windows.server.dns)