Main domain is redirecting to subdomain

apache-2.2mod-rewritesubdomain

I've a domain domain.com and made one sub domain 'forum.domain.com'. I'm using Apache2 and added one A record to the dns records and made virtualNameServer as:

<VirtualHost *:80>
   ServerName forum.domain.com
   DocumentRoot /var/www/vanilla
   <Directory /var/www/vanilla>
      # This relaxes Apache security settings.
      AllowOverride all
      # MultiViews must be turned off.
      Options -MultiViews
      allow from all
   </Directory>

   ErrorLog "|/usr/sbin/rotatelogs /etc/httpd/logs/vanilla-error.%Y-%m-%d.log 86400"
   CustomLog "|/usr/sbin/rotatelogs /etc/httpd/logs/vanilla-access.%Y-%m-%d.log 86400" "%h %l %u %t %D \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\""

</VirtualHost>

In the sub-domain, I've installed Vanilla Forum Software. But, now the problem is, whenever I go to http://domain.com or http://www.domain.com, it goes to http://forum.domain.com. There is .htaccess by default in forum.domain.com:

# Original
# If you modify this file then change the above line to: # Modified
<IfModule mod_rewrite.c>
   RewriteEngine On
   # Certain hosts may require the following line.
   # If vanilla is in a subfolder then you need to specify it after the /. 
   # (ex. You put Vanilla in /forum so change the next line to: RewriteBase /forum)
   # RewriteBase /
   RewriteCond %{REQUEST_FILENAME} !-d
   RewriteCond %{REQUEST_FILENAME} !-f
   RewriteRule ^(.*)$ index.php\?p=$1 [QSA,L]
</IfModule>

Please help. Thanks in advance.

Best Answer

http://httpd.apache.org/docs/2.2/vhosts/name-based.html

Using Name-based Virtual Hosts

Main host goes away

If you are adding virtual hosts to an existing web server, you must also create a block for the existing host. The ServerName and DocumentRoot included in this virtual host should be the same as the global ServerName and DocumentRoot. List this virtual host first in the configuration file so that it will act as the default host.

Related Solutions

Linux – Apache server keeps crashing regularly

I'm not saying this is what's happening but based on my own experience as a CentOS admin, it's most likely runaway apache/php processes taking down the server. I've seen this numerous times on CentOS 5. It's frustrating because there's usually not a trace of what happened in the log files. The machine just grinds to a halt due to physical memory and swap being sucked up by apache/php processes. You would think linux memory management or some daemon would jump in and say "hey stop" but it doesn't. It'll let apache grind your system to a halt.

Having said that, to see what's happening you'll need something that can monitor and log resource usage. I like to use a program called atop. Atop is a lot like the top program but it also takes a snapshot of resource usage at defined intervals. It's pretty simple to install.

wget http://www.atcomputing.nl/Tools/atop/packages/atop-1.23.tar.gz 
tar -zxvf atop-1.23.tar.gz
cd atop-1.23 && make install

Open /etc/atop/atop.daily with a text editor and change INTERVAL=600 to INTERVAL=60

Run the command /etc/atop/atop.daily from a command prompt to start it. Wait a few minutes and run atop -r /var/log/atop/atop_20091118 with the correct date of course.

Hit the t key to go forward in time and T to go back. Next time your server crashes do this and check the MEM free and SWP free lines. If you have memory problems these will be in red. Also look for numerous httpd lines under CMD. If apache/php is your problem there'll be a bunch of them.

If this is the case, I recommend looking at you're MaxClients setting in httpd.conf. If set too high, apache will gladly eat all of your memory causing your machine to crash. Apache/php can easily eat 40-50MB/process. If you multiply 40mb x MaxClients you'll get a rough idea of how much memory apache can potentially use. MaxClients usually defaults to 150 on CentOS so apache can potentially use 6GB of memory by default. This doesn't include memory your system needs for itself and other processes to run. Try setting it to a more realistic value based on the amount of memory you have like 40 if you have 2G of memory and see if that helps. Also if you have KeepAlive On, set KeepAliveTimeout to a low number like 2 or 3.

In my opinion CentOS's apache/php compilation is a real pos that should never have seen the light of day. It's buggy and crash prone. If you run a serious site, I highly recommend compiling your own version of apache/php or even using one of the newer high performance webservers like lighttpd or nginx with fgci php.

Apache – redirect suddomain to main domain

RewriteBase / 
RewriteCond %{HTTP_HOST} !^example.com$ [NC] 
RewriteRule ^(.*)$ http://example.com/$1 [L,R=301]

The above code looks at the HTTP host of the connecting browser. Note that .htaccess can only work on a request that can reach the webserver. This will work for forum.example.com, but only if forum.example.com actually loads the content in the directory that the .htaccess file resides in. If you do not have the DNS records set up (for example, a * A record or a forum A record) then it will not even go to the site at all, because the DNS is invalid. Also, Apache must be set up to load the site for that VirtualHost. So it must be listed in the Apache configuration as well before .htaccess can forward the URL as specified.

For your second question, in the RewriteRule part ^(.*)$, this only matches the file that is accessed off the server. The RewriteCond part only applies the rule on certain hostnames, then ^(.*)$ specifies that any request follow the rewrite rules.

So the above .htaccess code will apply for all requests after the / if the host does not equal example.com.

Let me know if you need any further explanation.

Best Answer

Related Solutions

Linux – Apache server keeps crashing regularly

Apache – redirect suddomain to main domain

Related Topic