[cobalt-users] CNAME problems on RAQ3

["INet" <info@xxxxxxxxxx>]

Hello all, I've been reading the archives all day now and have not been able
to come up with an answer to my problem so I thought I'd mail the list and
see if some charitable soul will give me a hand.

I tried to create a CNAME record on a RaQ3 in order to achieve the
following:

www.firstdomain.tld is a virtual domain,

www.seconddomain.tld is a second virtual domain,

on a server called ns1.server.tld which serves only 1 ip address and uses
name based virtual hosting on a RaQ3 box.

The purpose of the CNAME:

We need them two domains to share a directory on the file system (cgi), the
files will be the same, but the look and feel as well as the domain must be
different for each site.

Our solution to this problem was to create a CNAME record for a new host
name ( ww1.seconddomain.tld ) that would point to www.firstdomain.tld we
could then safely point links in www.seconddomain.tld to
ww1.seconddomain.tld/targetdir and use the files in the www.firstdomain.tld
document root.  The look and feel problem is of no consequence here, so I
won't expound on it.  The current issue is this:


The CNAME record for ww1.seconddomain.com takes us to the main website for
the server, namely ns1.server.tld instead of taking us to
www.firstdomain.tld which is where the CNAME points.

I noticed that this problem has occured before but there has been no
satisfactory solution.

Among other thing we have tried:

1) adding
include /etc/httpd/conf/otherinfo.conf
to the httpd.conf

and adding the otherinfo.conf file with

<VirtualHost 196.40.46.91>
ServerName ww1.seconddomain.com
ServerAdmin admin
DocumentRoot /home/sites/site2/web
</VirtualHost>

2) Changing the CName to an A record and pointing it to the IP.

We are still getting the same results.  Any help will be greatly
appreciated.  Specially advice on if the CNAMEs on Cobalts are completely
useless and if there is a workaround.  Again thanks.


Juan Carlos Murillo

INet - Web Development
http://www.inet.co.cr