[no subject]

Bob Toxen
bob at verysecurelinux.com               [Please use for email to me]
<a  rel="nofollow" href="http://www.verysecurelinux.com";>http://www.verysecurelinux.com</a>        [Network&amp;Linux/Unix security consulting]
<a  rel="nofollow" href="http://www.realworldlinuxsecurity.com";>http://www.realworldlinuxsecurity.com</a> [My book:&quot;Real World Linux Security 2/e&quot;]
Quality Linux &amp; UNIX security and SysAdmin &amp; software consulting since 1990.

&quot;Microsoft: Unsafe at any clock speed!&quot;
   -- Bob Toxen 10/03/2002


&gt; On Mon, 2004-11-29 at 19:40, Greg Freemyer wrote:
&gt; &gt; On Mon, 29 Nov 2004 09:51:34 -0500, James P. Kinney III
&gt; &gt; &lt;jkinney at localnetsolutions.com&gt; wrote:
&gt; &gt; &gt; I am looking at setting up a small non-local redundant webserver. The
&gt; &gt; &gt; net access for each node is through different ISP's so each node has
&gt; &gt; &gt; different IP's. In fact, there is nothing in common between the two
&gt; &gt; &gt; different networks. They have no common router.
&gt; &gt; &gt; 
&gt; &gt; &gt; The main site is serverd by a T1 line that is susceptable to an outage
&gt; &gt; &gt; caused by falling trees. I would like to make the outage as short as
&gt; &gt; &gt; possible by making the backup site live as fast as possible. Right now,
&gt; &gt; &gt; other than editing the DNS listing and waiting for the change to
&gt; &gt; &gt; propogate, I have no other way to do this.
&gt; &gt; &gt; 
&gt; &gt; &gt; Any suggestions?
&gt; &gt; &gt; --
&gt; &gt; &gt; James P. Kinney III          \Changing the mobile computing world/
&gt; &gt; 
&gt; &gt; If nothing else, you could try round-robin DNS.
&gt; &gt; 
&gt; &gt; That way roughly half of your dns quiries will go to each IP.
&gt; &gt; 
&gt; &gt; Then set your client TTL low so your users are requesting a new DNS
&gt; &gt; entry fairly often.
&gt; &gt; 
&gt; &gt; If one of your sites fails,  there is a 50% chance your users will go
&gt; &gt; to the other site with their next DNS request.  (ie. if you have M$
&gt; &gt; users, they do a dns request at least once per reboot.)
&gt; &gt; 
&gt; &gt; Greg


</pre>
<!--X-Body-of-Message-End-->
<!--X-MsgBody-End-->
<!--X-Follow-Ups-->
<hr>
<ul><li><strong>Follow-Ups</strong>:
<ul>
<li><strong><a name="01115" href="msg01115.html">[ale] failover planning</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
</ul></li></ul>
<!--X-Follow-Ups-End-->
<!--X-References-->
<ul><li><strong>References</strong>:
<ul>
<li><strong><a name="01064" href="msg01064.html">[ale] failover planning</a></strong>
<ul><li><em>From:</em> jkinney at localnetsolutions.com (James P. Kinney III)</li></ul></li>
<li><strong><a name="01106" href="msg01106.html">[ale] failover planning</a></strong>
<ul><li><em>From:</em> greg.freemyer at gmail.com (Greg Freemyer)</li></ul></li>
<li><strong><a name="01107" href="msg01107.html">[ale] failover planning</a></strong>
<ul><li><em>From:</em> cfowler at outpostsentinel.com (Christopher Fowler)</li></ul></li>
</ul></li></ul>
<!--X-References-End-->
<!--X-BotPNI-->
<ul>
<li>Prev by Date:
<strong><a href="msg01113.html">[ale] OT: Cable modem or naked DSL in Kennesaw</a></strong>
</li>
<li>Next by Date:
<strong><a href="msg01115.html">[ale] failover planning</a></strong>
</li>
<li>Previous by thread:
<strong><a href="msg01111.html">[ale] failover planning</a></strong>
</li>
<li>Next by thread:
<strong><a href="msg01115.html">[ale] failover planning</a></strong>
</li>
<li>Index(es):
<ul>
<li><a href="maillist.html#01114"><strong>Date</strong></a></li>
<li><a href="threads.html#01114"><strong>Thread</strong></a></li>
</ul>
</li>
</ul>

<!--X-BotPNI-End-->
<!--X-User-Footer-->
<!--X-User-Footer-End-->
</body>
</html>