[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [cobalt-users] Re: subdomains



Aeron Jarrett <ajarrett@xxxxxxxxxxxxx> wrote


> On Thu, 5 Apr 2001, Gerald Waugh wrote:
>
> <snip type=big></snip>
> |> RewriteEngine on
> |> RewriteCond %{HTTP_HOST}                !^ip.ad.re.ss(:80)?$
> |> RewriteCond %{HTTP_HOST}                !^www.123.domain.com(:80)?$
> |> RewriteRule ^/(.*)                      http://www.123.domain.com/$1
[L,R]
>
> <Response type=Unexperienced>
> Isn't the problem in this rewrite? You only have it rewriting TO www. Is
> that why it's not working for the host without the www? As far as I know,
> the www is just a name... you could call it spaghetii... It's not a
> keyword like in a programming language... and for that reason you SHOULD
> be able to leave it off... Unless you want the users to go to the www host
> on the 123 subdomain of domain domain.com...
> </Response>

The rewrite as outlined above will not cause the http://sub.domain.com
to fail,  it will cause the address bar on the browser to read
http://www.sub.domain.com
Leaving the last RewriteRule out will cause the browser address bar to read
http://sub.domain.com
The earlier poster that was having a problem with http://sub.domain.com has
a problem with DNS
www.sub.domain.com
DNS is working, but sub.domain.com
does not resolve, thus will not WORK.
there has to be dns 'A' records for both www.sub.domain.com and
sub.domain.com
Gerald