Date: Tue, 18 Apr 2000 10:38:03 +0100 From: Tim Priebe <tim@polytechnic.edu.na> To: bv@wjv.com Cc: freebsd-isp@freebsd.org Subject: Re: Failover question/idea/hint Message-ID: <38FC2CFB.102E40D7@polytechnic.edu.na> References: <200004171625.MAA39745@mail.wanlogistics.net> <44305.956004916@verdi.nethelp.no>
next in thread | previous in thread | raw e-mail | index | archive | help
> > An old client of mine is bringing up a portal site. They current have > > a T1 to their location, but the site is going to be put on a server > > at our co-location facility - which is inside an OC-48 connected facility. > > > > They are going to keep theri T1 and the current site as a development > > site, but they want to be able to use that site as a fail-over site > > in case the main site goes down. > ... > > I can't t see that the round-robin DNS approach would work, but if the > > primary DNS (located at tha main site) goes down, would that be enough > > to force it to the secondary name server - which I'm thinking could > > point to the backup site. One apporoch to automatic fail over is to bind the same ip address to the loopback interface of 2 or more systems, at different locations, and to route to them with a dynamic routing protocol. In your situation, it sounds like you would have to use a tunnel from the one site to the other. You would then have redundancy for server failure, but not if your network went down, unless you can have the tunnel implemented some distance from the co-location facility. Tim. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?38FC2CFB.102E40D7>