richardk wrote:The main reason is you could have totally seperate document roots instead of having the other domains inside your main domain's document root. You probably already have <VirtualHost>s, but they're just set to sub directories of your main document root.
I don't think you would get an speed increase or security increase (although you can probably add security settings if you manually set up <VirtualHost>s).
It's probably not a big deal, so think about it before you change. You might even be able to do a mix of the two.
Thanks again for your help, Richard. My only experience with hosts has been through shared host accounts, until I moved to my VPS at KnownHost. It appears that this is a different environment and I have more options on how to set things up. Unfortunately, I never knew there were other options.
I want to do it the most efficient way possible. I just had a friend contact me this morning and he wants me to build a couple sites for him and put them on a VPS of his own - same company I use. Even if I don't change the way I have been doing things on my own VPS (which it sounds like it might be better if I did change), I want to make sure I set him up properly.
The "mix of the two" might be best left to those sites I have duplicate domain names for - like thefloorpro.com and thefloorpro.net, etc. But because I seem to be wading into the unknown for me, I'll wait for guidance. Yours would be appreciated.
What are you going to use multiple IP addresses for? You can do IP based Virtual Hosts, but i don't think there's much point if you can do them based on the domain.
I was going to add IP addresses only so that some websites would have different IP addresses. I understand there is some debate as to its value when you do link trading. I have several flooring related sites, but they are all on the same IP. I thought if there was even the slimmest chance my ranking would improve if the IP's were different, I would do it. The cost is very reasonable. I didn't plan to use multiple IPs for the same site.
you wrote:I wrote:I am going to hold off on the 301 redirects until I hear back on these questions.
They won't do much harm. You would still want example1.enterprisejm.net redirected to example1.com, wouldn't you?
I heard back from the tech support person at KnownHost and they set up redirects that seem to work well. In the .htaccess file on the main account domain, enterprisejm.net, this is what they used:
- Code: Select all
Options +FollowSymLinks
DirectoryIndex index.php index.html index.htm
RewriteEngine on
RewriteBase /
RewriteCond %{HTTP_HOST} ^www.enterprisejm\.net$
RewriteRule ^(.*)$ http://enterprisejm.net/$1 [R=permanent,L]
redirect 301 /1foot http://1footinthegrave.com
redirect 301 /afpnet http://afloorpro.net
redirect 301 /ejmcom http://www.enterprisejm.com
The first rule, as you know, limits the domain to enterprisejm.net without the www. Then there are just simple redirect rules that send requests for any of the domain folders to the domain home page. And it's done in a way that preserves whether I have chosen to use www or not. In each domain folder is another .htaccess file that looks like this:
- Code: Select all
Options +FollowSymLinks
DirectoryIndex index.php index.html index.htm
Of course, there is more, depending if I have WordPress or other domain directives. But there is no
RewriteEngine on or
RewriteBase / lines. It works when I tested it on the 3 domains so far. I was in the process of adding all the rest of the redirects when I got notified of this topic reply.
As you say, it certainly won't hurt to continue with the redirects, so I will. But I do await any advice you may have concerning the structure I use in the VPS. Thank you very much for all your help.
Jim McClain