Re: [cobalt-users] [Raq3] "Secondary" domains/accounts

["WebWorkshop" <webmaster@xxxxxxxxxxxxxxx>]

I think editing the httpd.conf is definitely better than adding another
virtual site with an HTML redirect. It works a lot faster than an HTML
redirect, it doesn't goof up a browser's history list, and it's less clutter
in your server management page. Plus, once you get the hang of it, it's even
quicker to implement than adding a virtual site with an HTML redirect page.
(To be safe, make sure you back up your httpd.conf file before you try it.)

~ Chris Calabrese

----- Original Message -----
From: "Patrick Béart" <patrick@xxxxxxxxxxxxxxxxxxx>
Sent: Tuesday, August 29, 2000 8:58 PM


> Folks:
>
> I never did get an answer to this, so I'm reposting in case
> the issue was overlooked by anyone who might know.
>
> I have clients that have an average of 4 secondary domain
> names (permutations of their primary/main domain name), and I just
> create the accounts for each name.  For example, "Company.com" is
> primary, but "Company.net" is also setup with it's own account. Am I
> creating work for myself by doing this?
>
> Is the process, (Steven's below), BETTER than just creating
> the other domain names as accounts and using an HTML "redirect" page
> for any "secondary" domain names?
>
>
> >At 12:25 PM -0400 8/25/00, Steven Werby wrote:
> >...snip...
> >Then create the site as you normally would.  Create the DNS for all of
the
> >domains.  Edit httpd.conf for that VirtualHost.  Easy way to find
> >the line # is
> >to do:
> >...snip...
> >Add the following lines below the existing ServerAlias line:
> >ServerAlias domain2.tld www.domain2.tld
> >ServerAlias domain3.tld www.domain3.tld
> >
> >The restart Apache.  You can put multiple hosts per ServerAlias line
> >or one per
> >line - I do them as above b/c I like it organized that way.
>
>
> Patrick Beart