Thanks to all those who replied about this question. We ended up just
setting up a server to redirect httpd requests to the new location. Seems
it was alot easier to do that rather than to play around with routing
issues.
Cheers,
- Trevor
Message Posted at:
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
Maybe you can put a router running NAT to hide the new addresses behind
the old ones.
K.
Koen Zeilstra
Legian
---
You know you're a little fat if you have stretch marks on your car.
-- Cyrus, Chicago Reader 1/22/82
On Mon, 22 Apr 2002, Trevor Jennings wrote:
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
This is what I would do in your situation.. -Listing what i have
to do to keep the boss happy and save money for your firm.
1. Keep old IP's at the old datacenter, hitting live servers
at the new datacenter
2. Prevent the need to a second set of servers with DNS entries
seperate from the
5 matches
Mail list logo
