I mean at the TCP/IP level.
If both your servers are behind a firewall/NAT device, then you should be
able to use that device to forward all traffic destined for one IP to
another.
It depends upon the hardware/software you're using for the firewall/NAT
device but I think it's possible...and probably the simplest approach.
-Chris
________________________________
From: J Malcolm [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 2:30 PM
To: 'James Users List'; [EMAIL PROTECTED]
Subject: RE: Migrating Server to Another Box/IP
Do you mean go into every mailbox and set up forwarding? Or is
there some way to do it at TCPIP level?
If I forward mailboxes individually, what I am going to forward to?
My old box is currently configured to be "xyz.com". If I say to forward to
"xyz.com", Won't it confuse the system?
Also, for users who are stuck with a cached DNS entry for the old
box, they'll continue to come to the old box for a couple of days and not
see any of the mail that was forwarded to the new box during that time.
Granted, they'll see it in a couple of days, but for time sensitive mail,
that's not good.
Is there a way around that?
Jerry
-----Original Message-----
From: Chris Means [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 2:18 PM
To: 'James Users List'
Subject: RE: Migrating Server to Another Box/IP
Can you redirect traffic from the old IP to the new IP?
Seems like it would be the simplest solution.
________________________________
From: J Malcolm
[mailto:[EMAIL PROTECTED]
Sent: Thursday, April 01, 2004 2:14 PM
To: James Users List
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
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
