From owner-freebsd-isp@FreeBSD.ORG  Mon Sep  1 02:27:10 2003
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6317016A4BF
	for <freebsd-isp@freebsd.org>; Mon,  1 Sep 2003 02:27:10 -0700 (PDT)
Received: from exchange.wan.no (exchange.wan.no [80.86.128.88])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 20F5343FBD
	for <freebsd-isp@freebsd.org>; Mon,  1 Sep 2003 02:27:09 -0700 (PDT)
	(envelope-from sten.daniel.sorsdal@wan.no)
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 1 Sep 2003 11:24:33 +0200
Message-ID: <0AF1BBDF1218F14E9B4CCE414744E70F07DF30@exchange.wanglobal.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: Multi-Homed Routing
Thread-Index: AcNupYot8D3RmK0JRcuOg56KNhXNgQBxQTWA
From: =?iso-8859-1?Q?Sten_Daniel_S=F8rsdal?= <sten.daniel.sorsdal@wan.no>
To: "Kenneth Kabagambe" <kenneth@eahd.or.ug>,
	"Thomas Dwyer" <tom@dwyers.ca>, <freebsd-isp@freebsd.org>
Subject: RE: Multi-Homed Routing
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Sep 2003 09:27:10 -0000

[.snip.]
>=20
> this solution would work if you had alot of extra cash=20
> stashed away, just=20
> waiting to be used, which i dont think is the case here. yes=20
> bgp is the=20
> accepted solution but is way too expensive to implement.
>=20
Aye

>=20
> > However.
> >=20
> > You could achieve almost the same effect by using a script to
> > check if both gateways are up and if one goes down it automatically=20
> > changes the default route to the working ISP.
> > Then automatically adjust your DNS pointers to the new ip=20
> address(es).
>=20
> kudos to the venerable ping.

Kudos!

>=20
> >=20
> > Your public ip address(es) will change, and hence some people wont=20
> > be able to reach your site until their DNS's are updated. Some=20
> > people have caching DNS's that wont expire a record for a long time=20
> > to not generate alot of traffic and wont reach your site at all.
> >=20
>=20
> Stan, Cant someone use dyndns? wouldnt it be easier to use?

Sten :)

Dyndns is one of many similar solutions, of course someone could use =
dyndns.
I do believe that dyndns has the same "flaw" i describe above, but that =
is a
local dns management issue. So yes.