Totally newbie question

[Fryman]

Ok, I have a website. www.a.com. Hosting company charges me $9 for hosting service.
I then build another website. I buy a domain name for it, www.x.com

Can I host it where my www.a.com website is? Or do I have to open another account and pay another $9 each month?

Thanks for your help.

[Abdelrhman Fahmy]

That's depending on your Hosting Company and your package,
If they offer multiple domain per IP (most of hosting companies do) then you just need to change the DNS server of your new domain to the same DNS server of the old one and then log in to your Hosting account's control panel and add the new domain

The new domain should be forwarded to a directory at your current host the real path of your new domain will be like www.a.com/x but the users of your new domain will never see that but will see www.x.com or www.x.com/x .

[robert adams]

The new domain should be forwarded to a directory at your current host the real path of your new domain will be like www.a.com/x but the users of your new domain will never see that but will see www.x.com or www.x.com/x .

that is not necessarily so, I have several domains hosted on the same server as my main domain. I added them through my control panel. They cannot be reached by ht*p//maindomain.com/otherdomain

I have subdomains that are reached that way but not the actual domain names.

I think it really does depend on your hosting company and how they have their servers set up.

robert

[griz_fan]

Hi Fryman,

I actually just set up something exactly like what you're looking for. There may be several ways to accomplish this, but the method I used involved add-on domains. My host is a *nix host running CPanel, so the method described here may be specific to that particular environment.
In this scenario, I had www.domaina.com as my primary domain for my hosting account. I then registered www.domainb.com and pointed it to the same DNS servers as www.domaina.com. Through CPanel, I then set up an add-on domain, which created a new directory in my web root (/domainb) and created a sub-domain as well (domainb.domaina.com). Once DNS resolved, I could reach the new domain by either going to www.domainb.com or using the sub-domain route (domainb.domaina.com). In addition, I can also have email accounts for the new domain or sub-domain (i.e. [e-mail] or [e-mail]).

All-in-all, a pretty slick solution, if your web host supports it. And, as long as all your add-on domains aren't hogging system resources, you should be fine. If these domains look to generate a lot of traffic, or if you see yourself doing something like this with a bunch of domains, you may want to step up to a reseller's account, which will allow for a lot of domains, and more server resources.