Host name redirect?

[Bryan O'Neal]

Q1) Is the old box staying up?  i.e will duck or 192.168.1.3 be in
existence after this?
Q2) Are eagle and duck internal or external names.  Are they local to
your subnet or global FQDN's associated with real IP's?
Q3) Are you changing the domain name or just the boxes name?

	Example myprojects.cornerstonehomes.com is my global name for my
projects server.  This name has not changed since I set it up.  I have
changed the external and internal IP's many times, and even the name of
the box.  For example when I started myprojects.cornerstonehomes.com was
hosted on myprojects.cornerstonehomes.com, then on
fedorafive.cornerstonehomes.com and is now hosted on
cc9013b.cornerstonehomes.com.  I can get to this through any of three
"classic/testing" external "real" IP/port combinations and I can get to
it through one of two internal IP's.  Same box, same apache server, no
virtual hosting.

-----Original Message-----
From: plug-discuss-bounces at lists.plug.phoenix.az.us
[mailto:plug-discuss-bounces at lists.plug.phoenix.az.us] On Behalf Of
alex at crackpot.org
Sent: Tuesday, June 26, 2007 1:13 PM
To: plug-discuss at lists.plug.phoenix.az.us
Subject: Re: Host name redirect?

Quoting Alan Dayley <alandd at consultpros.com>:

> Scenario:
> (Names have been changed to protect the innocent, assuming there are
any.)
>
> Old server hostname: duck
> Old server IP address: 192.168.1.3
> New server hostname: eagle
> New server IP address: 192.168.1.9
>
> Old document URL (via http): duck/some/important/document.html
> New document actual URL (via http): eagle/some/important/document.html
>
> After the new server is in place any user or link that requests the
old
> URL, "duck/..." needs to be automatically redirected to "eagle/..."
> What do we change to accomplish this?

Add the following to duck's Apache configuration :

   Redirect / http://eagle/

Alternately, you could serve both hostnames from the same box, and set  
up 2 VirtualHosts (1 for each hostname), using the same DocumentRoot  
for each.  Then all content would be availble via either name.

NameVirtualHost *:80
<VirtualHost *:80>
   ServerName duck
   DocumentRoot /var/www/content
</VirtualHost>
<VirtualHost *:80>
   ServerName eagle
   DocumentRoot /var/www/content
</VirtualHost>

That might not work so well for some CMS systems, which want you to  
enter a hostname in a config file for certain URL-writing operations.   
I've also heard that serving the same content via multiple domains can  
hurt search-engine rankings.  But, it'd save you from having to keep 2  
boxes up.

And... I'm sure there are many other ways to accomplish your goals if  
either of these 2 ideas have problems.

alex
---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss at lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss