<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.technet.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Failover Cluster can delay DNS Registration for 10 minutes</title><link>http://blogs.technet.com/networking/archive/2008/11/07/failover-cluster-can-delay-dns-registration-for-10-minutes.aspx</link><description>Given the following scenario: Two Windows 2008 Servers running as an Active/Passive Exchange 2007 CCR Cluster. Each node is part of a multi-site cluster and each is located in a different subnet and point to different DNS server. The IP address needs</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>Failover Cluster can delay DNS Registration for 10 minutes | MS Tech News</title><link>http://blogs.technet.com/networking/archive/2008/11/07/failover-cluster-can-delay-dns-registration-for-10-minutes.aspx#3149258</link><pubDate>Fri, 07 Nov 2008 20:18:48 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3149258</guid><dc:creator>Failover Cluster can delay DNS Registration for 10 minutes | MS Tech News</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://mstechnews.info/2008/11/failover-cluster-can-delay-dns-registration-for-10-minutes/"&gt;http://mstechnews.info/2008/11/failover-cluster-can-delay-dns-registration-for-10-minutes/&lt;/a&gt;&lt;/p&gt;
</description></item><item><title>BlogMS Weekly Articles Published – 3rd November 2008 to 9th November 2008</title><link>http://blogs.technet.com/networking/archive/2008/11/07/failover-cluster-can-delay-dns-registration-for-10-minutes.aspx#3150347</link><pubDate>Mon, 10 Nov 2008 12:45:44 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3150347</guid><dc:creator>BlogMS - Official Microsoft Team Blogs</dc:creator><description>&lt;p&gt;203 Microsoft Team blogs searched, 88 blogs have new articles in the past 7 days. 252 new articles found&lt;/p&gt;
</description></item><item><title>re: Failover Cluster can delay DNS Registration for 10 minutes</title><link>http://blogs.technet.com/networking/archive/2008/11/07/failover-cluster-can-delay-dns-registration-for-10-minutes.aspx#3215836</link><pubDate>Fri, 20 Mar 2009 21:28:10 GMT</pubDate><guid isPermaLink="false">d5e57398-b9ef-4490-9955-07cbb4e4a80d:3215836</guid><dc:creator>Jeff Guillet</dc:creator><description>&lt;p&gt;PLEASE make this server side delay configurable setting. &amp;nbsp;Consider this scenario:&lt;/p&gt;
&lt;p&gt;CCR stretch cluster is configured using NODE1 and NODE2. NODE1 (the active node) must be brought offline for maintenance and the cluster is failed over to NODE2. NODE1 is brought online 30 minutes later and the cluster is failed back.&lt;/p&gt;
&lt;p&gt;In this scenario, clients would be unable to connect to the cluster for 10 minutes because the cluster record still points to NODE2. This is not acceptable for a highly available resource.&lt;/p&gt;
&lt;p&gt;I don't argue that this might be good default behavior, but you need to allow it to be configured according to business needs.&lt;/p&gt;
&lt;p&gt;Jeff&lt;/p&gt;</description></item></channel></rss>