[SOLVED] Looking TCP loadbalancing Solution that can Adhere to DNS TTLs on Backends
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Looking TCP loadbalancing Solution that can Adhere to DNS TTLs on Backends
I'm looking for something that is as good as haproxy for load balancing TCP which can register failures and failover etc.
But backend servers will be listed with a DNS name which needs to be re-resolved every so often. HAproxy from what I understand isn't able to do this without being restarted so I'm looking for another solution that's able to re-resolve the backend hostname every so often either specified by config file TTL or by adhering to correct DNS TTLs and thus not getting stuck on using one IP as the IP behind the hostname changes quite often and a lot thus need to find a solution to this problem.
Things that won't work -
Pound as not really a tcp load balancer.
nginx - I just don't want to use it seem like wrong tool for job to me, same basis with Apache as well and mod proxy type stuff
Varnish - same problem as haproxy
Balance - just tested and seems to keep the Same IP DNS resolved to on start-up of balance
I've been looking more at crossroads, Zen load balancer, LVS - Overkill maybe? Don't care if something gets the job done
Advantage - if the tool has some method of getting statistical data from it about whats its processing etc like haproxy has
Update:- OK - I've now just installed and got Crossroads running. It seems to work nicely with DNS (whether its resolving DNS for every single client connection, which i think it might be and will add latency thats annoying but at least its something that will work). What are peoples thoughts and feelings on crossroads? Its not something i've heard of before...
Last edited by helptonewbie; 08-09-2011 at 09:41 AM.