Re: Long failover time...

Than 90% of clusters were configured wrong to begin with :) Honestly, if DNS
is running properly you won't ever need a hosts file. Host files don't scale
very well or allow for easy changes!

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


"Kenny Speer" <kenny.speer@xxxxxxxxx> wrote in message
news:OvjOjNd3HHA.1208@xxxxxxxxxxxxxxxxxxxxxxx
Really? Hmmm. I've seen 90% of long failover times resolved by doing
this.

~kenny




"Rodney R. Fournier [MVP]" <rod@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:OdC0XMc3HHA.5984@xxxxxxxxxxxxxxxxxxxxxxx
Hosts file! No, DNS works nicely :)

Cheers,

Rodney R. Fournier

MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner


"Kenny Speer" <kenny.speer@xxxxxxxxx> wrote in message
news:uaFNDsH2HHA.5884@xxxxxxxxxxxxxxxxxxxxxxx
I thought it was recommended to put all cluster names/ips in the hosts
file located at:
%WINDIR%\system32\drivers\etc\hosts

By default, you don't want your cluster communicating over the public
(client access) interface and you don't want your cluster to fail just
because your DNS server goes down or is not accessible.

By adding each node to this file on both nodes, you won't even do a name
lookup via DNS since Windows uses hosts/lmhosts then DNS.

~kenny

"LOVEBEINGDBA" <LOVEBEINGDBA@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EC8A3B7D-E8D7-4B1E-BF4A-DD63E31750E9@xxxxxxxxxxxxxxxx
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: Long failover time...
    ... The routing stack in the host uses it in the following order: lmhosts, hosts, dns and wins. ... is it finds the host IP in the hosts file and no network requests are required. ... And it only effects those hosts you put in the file, hence you only add the cluster Nodes in the file. ... MVP - Windows Server - Clustering ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... http://www.clusterhelp.com - Cluster Training ... As for the hosts file. ... file) does nothing with a properly configured systems and DNS. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... I was explicitly stating that the cluster comm was NOT used just for the hearbeat. ... The routing stack in the host uses it in the following order: lmhosts, hosts, dns and wins. ... is it finds the host IP in the hosts file and no network requests are required. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... http://www.clusterhelp.com - Cluster Training ... The routing stack in the host uses it in the following order: lmhosts, hosts, dns and wins. ... is it finds the host IP in the hosts file and no network requests are required. ...
    (microsoft.public.windows.server.clustering)
  • 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)