Switching to a new remote server. How to do it without interrupting emails?

Posted on 2006-05-29
Last Modified: 2010-03-18

I have a corporate server at    (  www.myserver/~mycorp )  IP Address:

Switching over to   (www.newserver/~mycorp) IP Address: yyy.yyy.yyy.yyy

Before I change the nameservers for to point to the new IP address, I want to set it up so that there is no interruption to the live site and no email is lost or interrupted.

As far as the live site, can I set up the homepage at the old  server to redirect to www.newserver/~mycorp, then change the nameservers to point to the new IP address? Does that avoid the propagation time lag?

As for emails, how do I set up un-interrupted service. Both the old and new accounts will have the same domain name. Isn't there a way to use the IP address when setting up an account in Outlook Express, so I could have each user checking email at both accounts until the propagation time has run out?

Any help appreciated because I have to get this done in the next 24 hours and there are 11 cranky salespeople addicted to email that cannot survive any interruption.

Question by:alcibiades
    LVL 24

    Accepted Solution

    For the site, it is fine by first doing redirection and then change the DNS record.  For email, you will have not lost mail.  As long as your new mail server is up, you can switch the MX record to point to your new server.  While the propagation occurs, it takes a while for the world to know your new mail server.  At the mean time, some mail might still be delivered to the old server.

    There are two ways to handle this:

    1) Leave the old server running and setup your Outlook (Express) with IP to get the mail from the old server.  So what you do is that you check both new server and old server for mail.

    2) Turn of the old server immediately.  There is a very slight posibility of losing mail because normal mail sending protocol will retry with a certain period of time (24 - 36 hrs), by the time the sender mail server retry, the MX records should have been propagated properly.
    LVL 19

    Assisted Solution

    As long as possible before you make the change, adjust the dns TTL in your zone to something very low, like 5 minutes. This means that when you change the MX records etc that the rest of the world will comply with the change almost immediately. A low TTL means there won't be stale results hanging round on DNS servers around the world attempting to send mail to an old mail server.


    Featured Post

    Maximize Your Threat Intelligence Reporting

    Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

    Join & Write a Comment

    I have seen several blogs and forum entries elsewhere state that because NTFS volumes do not support linux ownership or permissions, they cannot be used for anonymous ftp upload through the vsftpd program.   IT can be done and here's how to get i…
    Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
    In this sixth video of the Xpdf series, we discuss and demonstrate the PDFtoPNG utility, which converts a multi-page PDF file to separate color, grayscale, or monochrome PNG files, creating one PNG file for each page in the PDF. It does this via a c…
    This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor ( If you're looking for how to monitor bandwidth using netflow or packet s…

    729 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    19 Experts available now in Live!

    Get 1:1 Help Now