Re: Long failover time...

"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

That has never been a recommendation that I have heard and it doesn't make any sense. DNS should be used for name resolution as hosts files just don't have the ability to meet most needs without having a bazillion copies of them everyone on every client that needs access.

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.

The heart beat does not care about DNS or any resolution whatsoever.

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.

which would save you how many milliseconds a year? Sorry, I am with Rod on this. Using host files doesn't make any sense.


--
Russ Kaufmann
MVP - Windows Server - Clustering
ClusterHelp.com, a Microsoft Certified Gold Partner
Web http://www.clusterhelp.com
Blog http://msmvps.com/clusterhelp

The next ClusterHelp classes are:
Sep 3 - 6 in Copenhagen
Oct 8 - 11 in New York

.

Relevant Pages

  • Re: Split-Brain DNS
    ... > What do I need to do to setup split-brain DNS for the company? ... > external DNS server I have setup on our DMZ, ... Deploying and Designing Active Directory [DNS Design, Migration, Cert Auth, ... Download details Windows Server 2003 Active Directory Branch Office Guide: ...
    (microsoft.public.windows.server.dns)
  • RE: windows nt to w2k3
    ... I have discussed with a cluster engineer on this issue and we think the ... the DNS side for name resolution. ... The domain controller meets the hardware requirements of Windows Server ...
    (microsoft.public.windows.server.migration)
  • Re: Long failover time...
    ... A perfectly configured Cluster can have any number of issues due to a misconfigured/non functioning DNS server. ... Also, remember, the hosts file has the private interface addresses ONLY, not the public. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... MVP - Windows Server - Clustering ... Second, in your hosts file, you put a hostname and IP address. ... Private Cluster Network: 192.168.x.x ... No DNS required. ...
    (microsoft.public.windows.server.clustering)
  • Re: Long failover time...
    ... I was explicitly stating that the cluster comm was NOT used just for the hearbeat. ... MVP - Windows Server - Clustering ... 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)
Loading