But you really wouldn't need actual TLDs to do this.
lucy24
7:58 pm on May 7, 2017 (gmt 0)
I want to have other domain names pointed to their own sub directories.
So you've got your physical directory structure: example.com/ example.com/domain1/ example.com/domain2/
What happens when someone requests example.com/domain1 instead of proceeding directly to domain1? That is, what do you want to have happen?
tangor
9:23 pm on May 7, 2017 (gmt 0)
Is there a practical purpose for doing this? In most cases, given the rather inexpensive start up costs for new domains, that would be the better choice.
ozstar
10:16 pm on May 7, 2017 (gmt 0)
Thank you all for the replies.
I was hoping that when they used the url for the primary domain they would land on the root index and if they used the 2nd domain name they would end up on the sub directory index.
If they used the full text, 'example.com/domain1', I assume it would land on that sub directory index.
Would that be correct?
The reason is I have a WHM plan for 100 doms $890 but I am cutting down and the next cheaper WHM is 30 doms $400. I have more than that and want to keep them but I can merge them as they are sort of related.
I could park all the names and have everything land on a Menu Splash page in root, then they can choose to go wherever, but I thought it better going direct.
keyplyr
10:28 pm on May 7, 2017 (gmt 0)
ozstar - seldom does anybody, except the site owner, use the domain/sub-domain name in a search or typed directly in the URL box. So your reasoning for this idea is really without merit.
ozstar
10:37 pm on May 7, 2017 (gmt 0)
I only answered the question from a previous poster. I always assume visitor will use the domain name period.
'What happens when someone requests example.com/domain1 instead of proceeding directly to domain1? That is, what do you want to have happen?'
keyplyr
10:49 pm on May 7, 2017 (gmt 0)
I always assume visitor will use the domain name period.
Very few, probably less than 20%, will search using the domain name or type the domain directly into the search box.
Most of your visitors will find your site by using keywords & phrases at Search Engines, or by following direct links (if you have any). The percentage of those actually using your domain name may be higher with return visitors.
Regardless, the reasoning to use TLDs as sub-domains remains flawed. Better to find another use for those TLDs.
tangor
11:54 pm on May 7, 2017 (gmt 0)
Assuming WHM means Web Host Manager, are you setting up a server to resell hosting? If so, check your documentation on how to do that properly.
ozstar
5:37 am on May 8, 2017 (gmt 0)
Hi,
No selling with these ones, they are just my own sites.
tangor
6:14 am on May 8, 2017 (gmt 0)
Which you want to set up as if they were WHM?
ozstar
6:36 am on May 8, 2017 (gmt 0)
No not really. It doesn't matter as they are my own sites anyway.
All my space is via the isp's WHM area.
I just wanted to eliminate some space by placing a couple of sites on the one domain account.
It seems it is a bit of a problem, so I may just set up a Menu page as the landing point and point all the parked doms to that page.
Visitors can choose from the menu what site they want to visit.
If so then all you need to do is to use your domain registrar's services and point the appropriate domain name (example2.com, example3.com, exampe4.com) at its own folder on example1.com/
I have done this with many domain names over the years, in fact I have more domain names pointing like this now than I have actual individual websites.
Of course this may not be what you are trying to do and I've completely misunderstood you.
ozstar
11:22 pm on May 8, 2017 (gmt 0)
Hi.
This is exactly what I need. As I am also a registrar reseller I will go see about this. If so, sounds like the 'ants pants' to me !
Thanks, I'll report back.
keyplyr
11:37 pm on May 8, 2017 (gmt 0)
@ozstar - as I said in the 2nd post of this thread:
You can file separate A records for each domain:
ozstar
12:51 am on May 9, 2017 (gmt 0)
Yes keyplyr, Thanks. I saw that but it didn't sink in then. I am new to this side of things and have not been getting easy straight answers from my host, that's why I am here.
My dom registrar chat says this..
<quote> it depends, because our end addon domain name on cpanel, the name servers should also be updated and this can be done through the registrar of the domain so you'll need to confirm it through your hosting provider for cpanel if you still need to update the name servers of the addon domain if yes, you can update it on our console
based on my experienced, it can be done via an A record or name servers...so if you already pointed the name servers no need to update the A records. You can confirm it with them </quote>
So is this in right for Cpanel?
Addon Domains of the primary site (example1.com)
New dom: example2.com Sub Dom: /example2/ directory Root: example1.com
Sorry to be a nerd, but first time in this Alligator pit.. :-)
keyplyr
1:39 am on May 9, 2017 (gmt 0)
So is this in right for Cpanel?
So ask your Host how you'd set it up with their Cpanel. Personally, I'd rather do it all with your Host using the A records; less chance of misunderstanding between the Host & the Registra. But it's good to know there's an alternative method.
ozstar
1:44 am on May 9, 2017 (gmt 0)
Yes I agree.
Just added it, so waiting for it to propagate now. Hopefully not too long.
Will report back. Really do appreciate the help thanks to all.
A great site !
ozstar
1:54 am on May 11, 2017 (gmt 0)
Yes all done. The Addon feature in Cpanel is really simple. It created a directory and named it the full addon domain name in root of the primary dom.
I placed the files there instead of the directory I had previously created in the public_html. Delted that and now all good, resolving fine. Email also works.