[EMAIL PROTECTED] wrote: > 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.
His options are heavily dependent on his budget etc, and he asked about simple load balancing and DNS gives you this without the need for some very expensive hardware, or extensive knowledge on how to cluster boxes etc until the cost v benefit gets to the point that training and/or equipment purchases verses extremely high availability look like the better option. In the case of VoIP, SRV records are the recommended way to go in most cases as the clients (that can deal with them, and most seem to be able to) handle things much more gracefully. Without knowing more information I just offered the cheapest/easiest solution currently available. -- 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."
