[cobalt-users] Re: forwarding

[Bruce Timberlake <bruce.timberlake@xxxxxxx>]

Johan Pretorius wrote:
> 
> for example i have an existing site which 'site1.com' i just
> acquired another domain which is 'site2.com' .
> 
> my question is how can i add a site in my raq4 that if go to
> 'site2.com' i can see the same content of my 'site1.com'.

Ensure that site2.com has DNS "A" records pointing "site2.com" and
"www.site2.com" to the same IP address as "www.site1.com". Then add
"site2.com" and "www.site2.com" in the Web Server Alias field in the
site1.com "Site Settings" screen.

This creates ServerAlias directive entries in the Apache configuration
file for site1.com, telling it to "answer for" site2.com or
www.site2.com...

So the Web Server Alias field for site1.com will have

	site1.com, www.site2.com, site2.com

listed there (site1.com needs to be added as a Web Server Alias so
Apache will answer properly if someone puts "site1.com" in their browser
and not "www.site1.com")  You don't need to add "www.site1.com" as an
Alias since Apache will already answer for that by default once you
create your site1.com domain.

On the RaQ3, people had to manually edit the httpd.conf file to add
ServerAlias directives and accompish this exact effect.  That's the
reason the functionality was added in the RaQ4 UI -- to keep you from
having to manually edit httpd.conf.  Use it as it was designed and
you'll be just fine. :)


FYI - If you need to also accept email for your site1 users at the
site2.com domain (i.e., no users for site2.com actually exist, but if
someone sends mail to Site1User@xxxxxxxxx, Site1User will receive the
mail in his/her inbox), ensure a DNS "MX" record for "site2.com" points
to "www.site1.com" (or whatever mail host you're using for site1.com). 
Then add "site2.com" and "www.site2.com" in the Email Server Alias field
for site1.com.  So the Email Server Alias field for site1.com will have

	site1.com, www.site2.com, site2.com

listed there.  site1.com and site2.com are listed so that the RaQ will
accept mail for "user@xxxxxxxxx" or "user@xxxxxxxxx". The
"www.site2.com" entry is there since the internal rewriting rules modify
the actual domain to be "www.domain.com", which then gets rewritten to
whatever the local username is.

Using the rules in /etc/mail/virtusertable:

Rule/Step 1: @domain.com %1@xxxxxxxxxxxxxx
Email for user@xxxxxxxxxx becomes email for user@xxxxxxxxxxxxxx

Rule/Step 2: user@xxxxxxxxxxxxxx localname
Email for user@xxxxxxxxxxxxxx becomes email for localname and gets
appended to /home/spool/mail/localname.  Which can then read by
localname's email program (Outlook, Eudora, etc).

-- 
Bruce Timberlake
Technology Engineer
Sun Cobalt Server Appliances
Sun Microsystems, Inc.

E: bruce.timberlake@xxxxxxx
U: http://www.sun.com/cobalt/