Results 1 to 2 of 2
  1. #1

    Question IP change / DNS issue

    Quick question... and it is driving us mad over here.

    We are moving to a new rack at our DC. Now the IP addresses will change.
    BUT.. we have a mailserver running, and all users are pointed at the current name "mailserver.domain.com" which itself is pointing to the old IP.

    So far so good...

    BUT we need to move that server to the new rack, and so we need to change the IP. But if we change the IP in the DNS, it will take till 24 hours for all the providers to propogate the new IP. For those users, the mailserver will be offline.

    How can we fix that properly? So that no-one has any serious downtime?

    Anyone got a clue on how to do so?

  2. #2
    Mailserver migrations, always fun I don't think I have ever completed a large scale migration without some users being affected. I would recommend you consider the following,

    Request that the DC route the /32 IP you'll be using in the new rack to the old rack for now so you can alias that IP on the server. Once it's been aliased, you can safely change your DNS to point to the new IP and the old IP will still be there for users who take longer to update their cache. The only downtime you will suffer in this scenario is the time it takes to physically move the machine.

    The alternative is to have that single /32 routed to the new cabinet along with the server.

    If neither one of these is possible, keep the router in the old cabinet and port forward the traffic to the new mailserver IP until the DNS has updated.

    Any reasonable DC will be able to accomodate one of these scenarios. If the physical distance between the two racks is beyond the distance of CAT5, consider creating a VPN tunnel between the firewalls in the two racks to expand your VLAN.
    ServiceFlex - High Performance Web Solutions

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •