On Monday, I'm relocating our co-located server to another co-location provider about 200 miles away. I'd just like to run through what I'm doing/planning to see if there are any holes in this plan....
First off, I've built a "mini" server to install in the current co-lo location for a week or two, we're paid up to the end of the month so I'm using the 2Us of space :). The "mini" server will be running secondary DNS, secondary MX and WWW services. The WWW services will be presenting a "site down" message for all domains hosted on the server. It will be living on the IP that the production server is currently on. Once the production server is on the move with me, a colleague will be updating whois records and DNS records to reflect the IP change accordingly. The plan is that whilst the production server is on the move, the "mini" server queues mail, says site down for those with cached DNS entries and redirects any new DNS queries to the new IP address. If the DNS queries are entirely new then they will get a server not found message for a couple of hours until the production server is successfully re-located. After a couple of days, the "mini" server should have no traffic going to it because the DNS entries should have propogated by then but I'm planning on leaving it in place for a week just in case. Does all this sound reasonable? Paul ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:5:177116 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
