[ previous ] [ next ] [ threads ]
 
 From:  "Mark Spieth" <mspieth at neod dot net>
 To:  <m0n0wall at lists dot m0n0 dot ch>
 Subject:  RE: [m0n0wall] Load Balancing Again...
 Date:  Sat, 29 May 2004 18:19:05 -0400
The biggest problem with round robin DNS isn't how it distributes the IP
addresses but caching when a machine goes down. If you have 3 machines
in DNS with the same A record and one fails, You would probably be able
to fix the machine before your TTL expired in DNS and everyone sees that
you removed the failed machine. This is why the round robin method
within ipnat is idea so if a machine fails you just remove it from the
round robin on the monowall box and no DNS updates are required.



-----Original Message-----
From: Fred Wright [mailto:fw at well dot com] 
Sent: Saturday, May 29, 2004 5:47 PM
To: m0n0wall at lists dot m0n0 dot ch
Subject: Re: [m0n0wall] Load Balancing Again...


On Fri, 28 May 2004, Eric Shorkey wrote:

> Round robin dns does do a pretty poor job of distributing connections.
> Mainly because the result gets cached by some isp's name servers and
> suddenly everyone from that isp is using the same server. If it's a
big isp,

Not necessarily - it depends on the clients.  With multiple A records,
the
client doesn't get *an* IP address, it gets a list of them.  If it
randomly rotates the list before using it, then the load gets
distributed.
This might be counterproductive if the DNS server is rearranging the
order
based on actual load, but that's extremely unlikely.

					Fred Wright


---------------------------------------------------------------------
To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch