Re: Long failover time...

"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...
    ... you don't want your cluster communicating over the public interface and you don't want your cluster to fail just because your DNS server goes down or is not accessible. ... > 'Public' to determine whether it accepts DNS registration updates. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... you don't want your cluster communicating over the public ... because your DNS server goes down or is not accessible. ...
    (microsoft.public.windows.server.clustering)
  • Re: two server shave same fsmo roles in same domain
    ... DNS Host Name: atlantis.baumeister.biologie.uni-freiburg.de ... [WARNING] ... The net card 'VMware Virtual Ethernet Adapter for ... Cannot find a primary authoritative DNS server for ...
    (microsoft.public.windows.server.general)
  • Re: DNS servers to be used
    ... I occasionally have the same problem with my VPN connections. ... I do like the response "There is No DNS server on adapters" the obvious lack ... The dhcp server tells my wireless adapter to use the router ...
    (microsoft.public.windowsxp.network_web)
  • Re: OWA 2003 Problem
    ... Your VM adapter is in the 192.168.20-range without DNS, ... "Luiz" schreef in bericht ... Ethernet adapter VMware Network Adapter VMnet1: ... Ethernet adapter Local Area Connection: ...
    (microsoft.public.windows.server.sbs)
Loading