Hi Trevor, Assuming that your servers have unique public IP addresses and you can get a small new address space from the colocation provider (for use as a NAT pool) then this would be technically feasible using twice-NAT. However, you would be paying your current colo provider for twice the bandwidth that you already consume plus your new provider. You would add hops, delay, packet loss, and complexity. If you do not have at least one spare server (assuming similar platforms) then you will require downtime whne you move each server anyway, so you could change the DNS entry then. Note that you must lower the TTL of DNS entries so as to let cached records expire in time for the change. Note also that if all traffic is web, then you might like to consider HTTP redirection as a technique in case your current DNS TTLs are already too long. rgds Marc
Trevor Jennings wrote: > > Hello, > > Where I work, we have a number of servers being co-located at one > location and are planning on moving those servers to another co-location > provider soon. My boss asked me why we could not, when we move the > servers, just place a router at the original ISP to redirect all traffic > from the original ip's to the new ip's rather than having duplicate > servers or adjusting the DNS at the same time. I told him that I wasnt > sure whether it was possible and was told by a friend that its not > really possible to do that. Can anyone confirm that or rather explain why > that is not possible? My Boss's theory was that we would have a router > with 2 ethernet ports and redirect the original ip's to the new ip's > through the second ethernet. > > Cheers, > > - Trevor Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=42223&t=42217 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
