Brad, After writing the text below I re-read your post and wondered if I missed something. Are you moving the IP number to the new box too? If not then the text below is valid.
------ A new domain that no one has ever used, and therefore isn't cached, should be pointed as an alias to the new IP location. You can have 10,000 domains all point to the same IP and if IIS or Apache or whatever you're using is properly configured they can all wind up on the same exact website, or have the webserver route the request to a specific site on the box based on the domain. The box only needs one IP. So, knowing that, you can build the new server up in advance with this new domain name (or even a new subdomain to the original, ie; www2.yourdomain.com) and test it. When the time comes, you change the DNS (after following all the other advice on this list, such as ratcheting down the TTL) for the original domain to the new IP, and make a change to application.cfm/cfc to cflocate the old site to the new domain (ie; www2.yourdomain.com). Thus: People whos DNS hasn't been refreshed will go to the old www.yourdomain.com and be sent to www2.yourdomain.com, which is the new box. People whos DNS has refreshed will go to the new box. If your DNS is on the old box that you're moving away from you may want to consider moving the zonefiles/DNS to your registrar. Both Godaddy and NetSol have this feature now. You "park" the domain on their boxes and then set the zone records in their interface. As for takiong the old site down, I'd wait more than a few days. Some ISPs and OSes are really very bad about refreshing. I know they're supposed to respect the TTL, but I've switched DNS in the past and sometimes the client complains that over a week later they're still winding up at the old site. Perhaps it's caching. Perhaps it's their OS not refreshing their local DNS. Perhaps it's a crummy ISP. Who knows. MIk At 11:40 PM 6/5/2007, you wrote: >For that to work wouldn't the new site have to have a static and unique >ip and the old site would redirect to that IP. Otherwise the user >couldn't get to the new site because their DNS server wasn't updated by >virtue of the fact that they had arrived at the old site. > >~Brad > >-----Original Message----- >From: Mik Muller [mailto:[EMAIL PROTECTED] >Sent: Tuesday, June 05, 2007 10:33 PM >To: CF-Talk >Subject: Re: How to handle the transition period to a new host? > >Buy an additional domain name or set up a subdomain that has never been >used before and cflocate to the new domain on the old site. > >Mik > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Create robust enterprise, web RIAs. Upgrade & integrate Adobe Coldfusion MX7 with Flex 2 http://www.adobe.com/products/coldfusion/flex2/?sdid=RVJP Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:280234 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
