Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

We have a situation where we'll be introducing a Load balancer in between the world and our pool of app servers. The DNS for our domain should point to the load balancer and it redirects traffic internally. The problem is that DNS propogation takes time and that we can't have any downtime.

Current Situation

x.y.z.123 is the APP server
DNS points to x.y.z.123

Expected New Situation

x.y.z.250 is the load balancer
x.y.z.123 is the APP server
DNS points to x.y.z.250

Which is the best way to do this ? I am ok with a solution having intermediate steps. Changing IP address of the APP server is not a solution.

share|improve this question
up vote 9 down vote accepted

Ahead of the time that I want to change the addresses on the records I will usually set the TTL on the records down to maybe 5 minutes. If the existing TTL's are, say, 48 hours then do the TTL change farther out than 48 hours before you want to change the addresses. This will give these records with a 48 hour TTL time to expire out of server / resolver caches and then become replaced with the 5 minute TTL. That means that the updated addresses are requeried every 5 minutes instead of 48 hours and the propogation of your changes is much quicker. After the change you can readjust the TTLs back to the original values.

share|improve this answer
Thank you very much. The readjustment based on current TTL was a nice tip too :) – Stewie Oct 10 '11 at 18:06

You should set the TTL (time to live) as low as possible. How you do this will vary from DNS provider to DNS provider. Make sure to do this at-least as far in advance as your existing TTL is so that everyone with the old TTL has a chance to get the new one.

Ultimately though if the app server's IP address is not changing is it going to be the end of the world if they go directly to the app server instead of through the load balance for a short amount of time?

share|improve this answer

Can't you just leave your existing publishing rule in place at x.y.z.123 pointing to your single application server and create a new publishing rule at x.y.z.250 pointing to your load balancer? I've successfully done so in an Apache load balanced cluster.

share|improve this answer
My domain has to point to the LB (250). I don't understand your explanation – Stewie Oct 10 '11 at 18:07
@Stewie, so long as your current app server is still responding to requests to x.y.z.123 for, then changing the DNS to point to x.y.z.250 shouldn't hurt during the TTL window--some clients will use x.y.z.250 and others will use x.y.z.123 but all would succeed. That said, I would use the TTL-adjustment described in the top answer above in any case. – daveadams Oct 10 '11 at 18:56

Your Answer


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.