- NAT/Forward TCP/IP connections from old to new,
- setup james on old machine (i.e., former IP Address) to use remote delivery to the other machine's IP address,
- setup different MTA on old machine (address) to relay to new machine,
- etc.
(Part of the etc. is my solution to the same problem: sharing the database with two James instances over a VPN/SSH/SSL tunnel)
Robert Taylor
Danny Angus wrote:
mited.
If you have control over your dns entries reduce the TTL of your primary A record to half an hour or so, then it should propogate through four levels of cache within two hours.
You could also use a packet filtering firewall to forward all the TCP/IP traffic on certain ports to another machine (eg iptables on linux or a standalone GNAT firewall) Even if you don't care about security this scenario is a real good reason for having a firewall/router as your front line.
d.
|---------+----------------------------> | | "J Malcolm" | | | <[EMAIL PROTECTED]| | | ms.com> | | | | | | 01/04/2004 09:14 | | | PM | | | Please respond to| | | "James Users | | | List" | | | | |---------+----------------------------> >---------------------------------------------------------------------------------------------------------------| | | | To: "James Users List" <[EMAIL PROTECTED]> | | cc: | | Subject: Migrating Server to Another Box/IP | >---------------------------------------------------------------------------------------------------------------|
I am planning to move my domains to another box and another IP address. Iâm well aware of the propagation delays when a domainâs IP address changes. I need to minimize the disruption to my users and obviously not lose any mail in the process. Is there any âbest practicesâ for how to do this?
Details: when I actually throw the switch, some mail will begin going to the new box fairly quickly while some mail from servers using a cached DNS entry for the domain will continue to send to the old box until the cached address expires, which could be a couple of days.
Likewise, some usersâ mail program will almost immediately start going to the new box while others may stay on the old box for a couple of days.
So the question isâ is the right answer to just let whatever happens happen for a couple of days, and then when the dust settles reprocess any leftover mail on the old server to get it routed to the new server? The obvious problem with this is the potential for mail that wonât be seen for couple of days. Is there a tried and true better way.
Thanks.
Jerry
*************************************************************************** The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Li
This footnote also confirms that this email message has been swept for the presence of computer viruses.
**************************************************************************
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
