Date: Sun, 29 Apr 2001 08:06:02 -0700 From: "Kulraj Gurm (bosa.ca account)" <kulraj@bosa.ca> To: "Ken Bolingbroke" <hacker@bolingbroke.com>, "Ted Mittelstaedt" <tedm@toybox.placo.com> Cc: <questions@FreeBSD.ORG> Subject: Re: Redundant Internet connections Message-ID: <002901c0d0bd$e8466de0$64c8a8c0@asknet.com> References: <Pine.BSF.4.21.0104290057220.87921-100000@fremont.bolingbroke.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> However, if ISP A dies on Wednesday, ISP B takes over the slack. If ISP B > dies on Friday, ISP A is handling things anyway. True, there's the chance > that both ISPs will die on the same day, but the likelihood of that is > definitely much lower than the liklihood of being without access > altogether if you have only ISP A. It doesn't guarantee 100% uptime, but > it does get a lot closer at much less expense than it would cost for a > 99.95% SLA. I am pondering taking a second T1 with a different telco for redundancy, and your discussion has so far been interesting. I am a little confused however; maybe just my lack of understanding, but all your discussion on redundancy has been focussed on out bound traffic - where I can conceptually see it working. But what are the DNS implications? We have numerous clients; and many of them have numerous domains. I generally assign an IP per client and virtual host as many sites as they want on the single IP. This is all through one telco at the moment. When a second telco enters the picture, and I get a different IP range assigned to the new T1. When the first network is down - all hosted sites will still be inaccessible. What would be the solution to this scenario. Regards, Kulraj Gurm To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?002901c0d0bd$e8466de0$64c8a8c0>