2

We added SSL and had to change our IP address. This didn't go well. Users can't reach the site, they have to flush their DNS, restart their computers, web services using our PUSH are not responding etc.

Is there any way to change IP addresses in a friendly manner without asking people to reboot, restart networking, reset their router and so on.

4

A few days before your cutover to the new IP address:

  • Lower the TTL on your DNS records, so that when you DO make the change, it is updated around the DNS system quickly. A TTL of 10mins or so is a good tradeoff
  • adding the new IP to your existing site so that it can run on both the old and new. You mention SSL, so I'll assume it's a web server of some sort, which can normally be configured pretty simply to serve on multiple IPs

A few days later (or basically when you're sure the original TTL on the DNS record has expired and DNS servers now have your lower TTL cached), update the DNS record to become your new IP. You should start to see traffic via your new IP pretty quickly.

Leave it this way for a few days as DNS caches expire and pickup your new IP and start using it. Once you're happy that you're seeing a normal level of traffic via your new IP, remove the old one from your server.

There really isn't a quicker way to do it without experiencing some level of interruption to users.

8

Lower the TTL on the appropriate records and make the change after hours or at a time when you have the least traffic.

  • 1
    One thing to add - if possible, the most "seamless" method is to run on both addresses while the DNS is in an inconsistent state (immediately after the update). – Shane Madden Apr 29 '11 at 19:00

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

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