Welcome to WebmasterWorld Guest from 220.127.116.11
Forum Moderators: phranque
I was wondering if anyone around here does this (multiple domains on one hosting account). Does this refer to multiple completely seperate domains? For example, could a person host a blog, a small business site, and a info site on the same account, even though the three (or more) were totally unrelated?
And themore important question: is there a reason to do, or not to do, this? Any Google problems or the like?
Forgive me if this seems like something one ought to already know, but it's been a while since I've had to worry about server issues and no two hosts word their service descriptions the same.
Most hosting companies can do this for a small additional fee. Otherwise, they usually all offer multiple domains pointing to the same content included in the main package.
The sites will all share the same IP address, and if the server goes down, both sites do - but in general it is a very good way of utilising otherwise wasted resources.
Best bet is to always email all the hosting companies on your shortlist with a set of questions such as this before selecting a company - it helps make the choice when you can guage how serious and knowledgeable the staff are. Put 'em all in a visible CC and they'll know who they're up against and you'll see who comes back with the best deal!
... and in the event one site should get banned/penalized - the rest could likely follow. Another example of not putting all of your eggs in one basket.
[edited for grammer]
but in general it is a very good way of utilising otherwise wasted resources
<<< Does this refer to multiple completely seperate domains?
Yes, but you have to make sure your webhoster actually gives you real separate domains, with separate IP addresses, most don't.
<<< For example, could a person host a blog, a small business site, and a info site on the same account, even though the three (or more) were totally unrelated?
Yes. If you have the right hoster.
<<< And themore important question: is there a reason to do, or not to do, this? Any Google problems or the like?
No, there's no reason not to do it if you have a high quality hosting company that gives you separate IP addresses on each domain. That's actual, real IP addressses, from different IP blocks, randomly assigned.
That's actual, real IP addressses, from different IP blocks, randomly assigned.
It's tin-foil hat time ;) There's no need to go to these lengths unless your site is in highly-competitive sector where every minor variable makes a difference.
Half the world is using shared IP addresses. There is one hosting company I know that has 30,000 sites on one IP address. Some are related, others clearly are not.
I'm usually happy to host smaller sites such as blogs, info sites and the like on shared IP addresses from reputable hosting companies with strict no-spam policies. A commercial site should have its own IP address, but demanding random addresses from different IP blocks is overkill unless you're actively trying to mask a network of sites.
When I signed up with my hosting company, they offered plans for 2, 4, 6, 8 or 12 domains. (They have changed their plans a bit since then.) I actually graduated from 2 then 4, then 6 and finally to 8 as my project list grew. All 8 domains share the same IP and I have a PLESK control panel to manage them.
One thing to verify that I thought was important was the ability to switch out domains. I wanted to make sure I could host example.com in one slot and then at some point in the future, dump it and host myexample.com in that slot. That was no problem and I have had a need to do that.
There have been some minor outages and of course that means all 8 of my domains go down. But, those have been few and far between.
What's really nice is the ability to share disk space & bandwidth between them. One of those is a disk space hog, another is a bandwidth hog and the other six don't use up much of anything, so I can pull space and bandwidth from those 6 and assign them to my 2 hogs. :)
Message me if you'd like to know who my host is.