That would achive load balancing, but you would have to have very short ttl's on your dns records. In other words if you have a 60 second ttl there will be users who cannot access a dead webserver until 1 minute after it's been found to be dead. Dead server detection would add more time to that as well.
Now if you include cluster software that moves the ip address to a surviving server you've shortened the down time. Sent from my BlackBerry device on the Rogers Wireless Network -----Original Message----- From: Duane <[EMAIL PROTECTED]> Date: Wed, 21 Mar 2007 16:07:12 To:Chuck Mariotti <[EMAIL PROTECTED]> Cc:[email protected] Subject: Re: [on-asterisk] Load Balancer? Chuck Mariotti wrote: > I really need something simple/easy since I will not be the only one > administrating this. If you want simple simple why not just use DNS round robin? Some DNS servers have extensive modules on the backend to monitor servers (up/down) and adjust results being returned accordingly. -- Best regards, Duane http://www.cacert.org - Free Security Certificates http://www.nodedb.com - Think globally, network locally http://www.sydneywireless.com - Telecommunications Freedom http://e164.org - Because e164.arpa is a tax on VoIP http://www.freeauth.org - Enterprise Two Factor Authentication "In the long run the pessimist may be proved right, but the optimist has a better time on the trip." --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
