[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-developers] Sub Domains
- Subject: RE: [cobalt-developers] Sub Domains
- From: "Jim Carey" <ozbcoz@xxxxxxxxxxxxxxxx>
- Date: Fri Jan 26 23:14:01 2001
- List-id: Discussion Forum for developers on Cobalt Networks products <cobalt-developers.list.cobalt.com>
> "Gerald Waugh" <gerald@xxxxxxxxx> writes
> Excuse me, while I talk to myself;
> I have seen this solution to building a subdomain several times on
> this list, and I don't believe it (the solution) builds a subdomain.
> It must build a new virtual site "mysub.domain.com"
> and that is not a subdomain. It may look like a subdomain
> because it has a URL http://mysub.mydomain.com but the
> DocumentRoot directory does not fall under mydomain.com
>
> Correct?
correct - guess I have taken it to be the popularly quoted version of
subdomains - rather than the strict one of being within the mydomain file
structure.
I have understood the original question to be how to set up a subdomain
(taken to mean a new hostname.domain combination that points to a site).
Once the subdomain is setup and pointing to an ip, a web site can be created
in the normal way with mysub.mydomain.com as its name. This will be
addressable on the web - eg my site webmail.iluvoz.com which is a different
site from www.iluvoz.com (so I stopped the reply before how to create the
site - but I didn't think he was asking for that)
If the customer wants to point the new hostname(subdomain).domain to a
directory within an existing site I would use the excellent archive email
you pointed to
http://list.cobalt.com/pipermail/cobalt-users/2001-January/029733.html
guess it's a question of semantics - some ppl refer to subdomains as
directories within an existing site - some take it to mean how to set it up
for a new site.
Must admit though that all in all I like the answer you provided in the
above link - covers both bases :-) (and is also "more correct" :-)
Jim Carey