Date: Mon, 30 Apr 2001 21:39:19 -0700 From: "Ted Mittelstaedt" <tedm@toybox.placo.com> To: "Kulraj Gurm (bosa.ca account)" <kulraj@bosa.ca>, "Ken Bolingbroke" <hacker@bolingbroke.com> Cc: <questions@FreeBSD.ORG> Subject: RE: Redundant Internet connections Message-ID: <000501c0d1f8$afae3c60$1401a8c0@tedm.placo.com> In-Reply-To: <002901c0d0bd$e8466de0$64c8a8c0@asknet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>-----Original Message----- >From: Kulraj Gurm (bosa.ca account) [mailto:kulraj@bosa.ca] > >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 No it HAS NOT. Reread the message - I say "in and outbound traffic" many times in the response. - 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. > The solution is to have both T1's go to the same ISP via different Telco's and run a routing protocol like OSPF with that ISP. Or better yet put your virtual servers in a co-locate facility that has lots of redundancy in it and quit throwing money on Telco circuits. Ted Mittelstaedt tedm@toybox.placo.com Author of: The FreeBSD Corporate Networker's Guide Book website: http://www.freebsd-corp-net-guide.com 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?000501c0d1f8$afae3c60$1401a8c0>