mailing list archives
Re: Failover internet connections, and implementation...
From: c0unter14 <c0unter14 () gmail com>
Date: Wed, 24 Oct 2007 07:05:31 -0700
As evident from earlier replies, the inbound traffic provisioning will
need some work done to be useful in case of a failover. If you are
willing to spend, there are third party solutions that will do this
for you as a lot of people have sent you the links. If not, you can
also do some tricks with your existing firewalls to get it to work.
for e.g. Checkpoint has an inbuilt option for ISP redundancy. In case
of Juniper, you can use a combination of 2 (or more) default routes
with different weights and "track-ip" options to make a failover ISP
redundant system, however in both cases provisions will be needed for
inbound traffic due to routing issues. Some of the third party
solutions mentioned above work very well, and should be preferred if
you have the money (which usually nobody has). However, if you want to
get it done with your existing infrastructure, it is entirely possible
but will again depend on what devices you have.
On 10/23/07, jam () zoidtechnologies com <jam () zoidtechnologies com> wrote:
On Tue, Oct 23, 2007 at 02:05:44PM -0700, David Gillett wrote:
Neither of these will work if you host the company's Internet-
facing servers (web, email) on the network, because DNS entries
(cached all over the place) will still be pointing at your primary
you can change the zone file so that it has a much shorter timeout-- that
way if there is an outage and you need to change the zone you can do it with
minimal delay... change it from 3 days down to 30 minutes, for example, and
your changes should propagate much quicker.
http://zoidtechnologies.com/ -- software that sucks less