Re: [cobalt-users] RAQ4 Name Based Hosting

[Alfredo <alfredo@xxxxxxxxxxxxxxx>]

Bill, I've never heard of that "site showing other site's pages 
problem" on any of the newer Raqs. What a nightmare that must have 
been!

To "publish" a site that's still domain propagating using name-based 
hosting you need a workaround. You've already been told about a 
couple of workarounds. The one we use here has also been described in 
this list in the past but I'll describe it again:

Say your client's domain is client.com and the site will have the url

www.client.com

And say YOUR server has a domain called micke.com.

Okay...

go to the DNS records in the GIU and set up:

an A record for client.com ----> IP address
an A record for www.client.com ----> IP address
an MX (if you need it) for client.com -----> client.com

And realize that you just did this because later on (if you're like 
me) you'll forget you didn't. :-)

NOW, you're gonna set up a test site for the client.

Set an A record to

client.micke.com ---> IP address

Nothing more. Save the new dns settings.

And then go to the server management screen in the GUI and set up a 
new site with the host name "client" and the domain name "micke.com" 
and you can enable cgi and ssi if you want and that's it.

If you have already set this site up under the real (permanent) url 
name, just change it to the above. Url names on the site settings are 
only aliases. The real site name is its site number and that won't 
change with these new settings.

Save

Let the client upload by ftp to the site you've created (since they 
do this with the username/password combo, they don't ever have to use 
a url or site name) and then when they want to view and test it, they 
should use

client.micke.com

Now, when the domain propagates to your server:

All you do is change the record that set up the site. Where you have 
"client", change it to "www" and where you have "micke.com" just 
change that to client.com. And make whatever modifications in 
services you want to make for the final site. Save that and this site 
has just changed urls. :-)

Then you just eliminate that old A record (the one with 
client.micke.com) and you're all set. (Because you already set up the 
domain records for this permanent url, right?)

The only caveat is if they run cgi they must remember to change any 
"url" configurations in the scripts and any full url calls from the 
site's pages to the scripts to the new, and permanent, url. I mention 
this because I forget it every single time I do this!

By the way, there is no time delay when you do this. The moment you 
change and save it, it goes live.

Not perfect but, on the Raq, it's as good as anything I've seen around.

Hope this helps.

Alfredo


> ----- Original Message -----
> From: "WebSite Creations" <main@xxxxxxxxxxxxxxxxxxxx>
> To: <cobalt-users@xxxxxxxxxxxxxxx>
> Sent: Thursday, September 28, 2000 11:03 PM
> Subject: [cobalt-users] RAQ4 Name Based Hosting
>
>
> >  Hello Ladies and Gentlemen,
> >
> >  I have searched the user list archives and cannot find an answer to this
>  > question.  I'm sure someone who reads this will have an answer though.
>  >
>  > We are considering 'name based' hosting on our RAQ4 server (using 1 IP for
> >  several sites).  I have used this before on a RaQ2 and found the following
> >  problems;
> >
> >  1.  The shared sites seemed to get mixed up sometimes where as
> >  'domain1.com' would show files for 'domain2.com'
> >  2.  When setting up a new account on a shared IP, the user could not view
> >  their files via a web browser until the domain name became active.  (this
> is
> >  possible with a dedicated IP by typing in the IP# in a web browser, but
> not
>  > with shared IP hosting)
>  >
--
People-Link/Institute for Mass Communications
461 54th Street   Brooklyn NY 11220   718 567-8463
Communications for a Better World...and for the People Who are Building One!
Members, Local 1180, Communications Workers of America, AFL-CIO