Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

We have a big pool of web servers for a particular web application we develop on. Our clients currently point there domain or a subdomain using a A record to one of our servers. As we are growing we need to be able to dynamically move the sites to different servers on different IPs which means asking the client to update their DNS, which we don't/won't want to do. By dynamically I mean if a server goes down we want to re spawn the data on a new server, change where the domain points to and have the application back up with in seconds/few mins.

My first thought was to use our DNS servers but many clients can't change their NS servers to ours. And can only add an A record to a single static IP.

So I had a look into using a layer of proxy's, like HAProxy which can route the traffic by hostname. The problem with this is I need to be able to add a new domain every few seconds and HAProxy uses a config file and you have to reload the service to apply the new config. Which won't work well doing it every few seconds.

Is there anyway I can do this with a proxy application or DNS application?

share|improve this question

1 Answer 1

If they point always to IP with 'A' record, then DNS is not help here.

share|improve this answer
    
They don't this is the point, they may change several times a day and I need a way of keeping a domain connected to the right server. –  dx282 Feb 20 '12 at 11:54
    
Then you need to redirect based on HTTP header, http load balancer. Then you obviously have problem with your statement "won't work well doing it every few seconds.". Have you tested that? –  Jiri Xichtkniha Feb 20 '12 at 12:15

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.