Discuss mailing list

[<kennytaylor AT runbox.com>]

Load balancing inbound traffic is the trick.  The right way to do it is BGP 
routing, which requires expensive address blocks and cooperative ISPs.  That 
way you own a set of addresses and advertise that set to both ISPs.  Pricey 
and hard to get.

At the day job, we use an appliance called Fatpipe Warp.  I'm not a big fan 
of proprietary stuff, but it takes a neat approach.  It has three WAN 
interfaces and acts as the DNS server for the domain.  When a client does the 
DNS lookup for "www.domain.com", the query goes to both WAN IP addreses.  The 
DNS response has a very small TTL--10 seconds I think--and replies with only 
the IP addresses of the WAN interfaces that are in an UP state.  It only 
works for applications accessed with a hostname, and TCP sessions break when 
a WAN link goes down.  But it's a neat trick:)

Kenny

----- Start Original Message -----
Sent: Fri, 22 Feb 2013 20:53:02 -0700
From: Jeff Taylor <shdwdrgn AT sourpuss.net>
To: discuss AT lists.opennicproject.org
Subject: Re: [opennic-discuss] Hosting Tier-2 DNS server

> I use shorewall for my firewall.  You can add in a program called LSM
> which will monitor and manage multiple internet connections.  It takes a
> bit to set it up, as there is no good documentation on it, but once you
> have it working it is great.  When both of my connections are online,
> outgoing traffic uses round-robin between them.  If one of the
> connections fails, LSM will do failover in a matter of seconds.
> 
> 
> On 02/21/2013 02:13 AM, Lenny Guy wrote:
> > 3) I have, but I don't know how to do rolling
> >
> 
> 
> 
> --------
> You are a member of the OpenNIC Discuss list. 
> You may unsubscribe by emailing discuss-unsubscribe AT lists.opennicproject.org

----- End Original Message -----