The following settings can be used for a general cluster configuration. Do note that you want to be EXTREMELY careful in setting high values here so as to not cause a non-detection event where the cluster does not failover as expected: Likewise, turning up the sensitivity may cause false failover events to happen when not needed:

1. If any nodes are currently paused, unpause them all using the failover cluster MMC
   
2. Set the following cluster properties on the passive node(s) from the command line:
   

   cluster /prop SameSubnetDelay=1000
   cluster /prop SameSubnetThreshold=10
   cluster res ClusterName /priv HostRecordTTL=300
   cluster res AnyOtherClusterName /priv HostRecordTTL=300

3. Also set the following cluster properties for the individual node via the command line:
   

   cluster /priv HeartBeatLostInterfaceTicks=10:DWORD
   cluster /priv HeartBeatLostNodeTicks=10:DWORD

4. Stop and start the cluster service on each node to confirm the settings have taken effect

Do note that the general settings and how to set these are found at the following link below:
What has changed for Windows 2008 and the heartbeat network?

Speacial Note: Dynamic DNS and Windows 2008 Failover Clusters

If you are seeing random issues here where DDNS is failing even after the changes are made above you can try going the alternate route and performing the following changes:

• Change the cluster DNS registration TTL's to to reflect a (1) day expiration:

  cluster res ClusterName /priv HostRecordTTL=86400
  cluster res AnyOtherClusterName /priv HostRecordTTL=86400

• Uncheck the "Register this connection's addresses in DNS" in the advanced DNS properties tab on all NIC's for all nodes of a cluster
  
• Choose the "Disable NetBIOS over TCP/IP" option in the advanced WINS properties tab on all NIC's for all nodes of a cluster

NOTE - This change is basically making the DNS registration of the cluster's network name valid for the prescribed time frame. If the IP Address is changed manually on purpose, you may need to restart the cluster and/or clear out the DNS cache to ensure this gets updated to the latest IP Address. Also, proper testing should be performed to ensure this option is valid in any particular customer's environment.