Addon domains differing only in tld/extension

[cPdans]

Hello Everyone,

I've noticed some confusion regarding add-on domains. I was assisting a customer this morning and he wanted to add some add-on domains: domain.net and domain.biz. These were for differing purposes and needed to be directed to different directories. The general misconception is that this isn't possible because they will both generate subdomains that are the same: domain.maindomain.tld. This is not the case if you use different Subdomain/FTP Usernames. This field is autopopulated by the first portion of "New Domain Name". So there is a confusion about this. So if you have domain.net and domain.biz and set the usernames to john and jack, the subdomains would be john.maindomain.tld and jack.maindomain.tld respectively. I have seen this mentioned at least a couple times as a reason for changing the way our add-on domain system works and I just wanted to point out that there IS a way to make this work. Hopefully, this alleviates someone's troubles in the future.

Thank you for choosing cPanel.

[ms308680]

that is not quite the main issue, the main issue is the creation of subdomains for add-on domains in the first place. There is no reason for this. A really quick work around for this is if they cannot get to the subdomain, so you don't have to worry about comtamination of the search engine. So how does everything on the web know where to go? DNS

use the advanced dns editor and delete the subdomain entries, while you cannot delete the subdomains from the sub-domain manager, you can delete the subdomains from the dns manager. so to the world that subdomain does not exist.

Just be aware that if you ever have to reset your dns zone back to origional, then it will restore these enteries.

[cPanelTristan]

Since I am not seeing your name listed in the following feature request, ms308680, you may wish to post in it to lend support:

http://forums.cpanel.net/f145/true-m...-a-138917.html

This request deals with setting up multi-domain support rather than a system of subdomains tied to addon domains for addon domain existence.

[tdave888]

that is not quite the main issue, the main issue is the creation of subdomains for add-on domains in the first place. There is no reason for this. A really quick work around for this is if they cannot get to the subdomain, so you don't have to worry about comtamination of the search engine. So how does everything on the web know where to go? DNS

use the advanced dns editor and delete the subdomain entries, while you cannot delete the subdomains from the sub-domain manager, you can delete the subdomains from the dns manager. so to the world that subdomain does not exist.

Just be aware that if you ever have to reset your dns zone back to origional, then it will restore these enteries.

Err, that might solve half of the problem. I tried deleting the subdomain's dns record using the simple dns editor in cpanel but page still opens up, maybe dns refresh issue. Time will reveal.

The other half of the problem is when
hosting-account's main domain: /penisenlargement.com
add-on: /nurseryrhymes.com
then google might still be indexing /penisenlargement.com/nurseryrhymes/humptydumpty.html
CMIIW

Anymore tricks to prevent the above? Thanks.

[cPanelTristan]

Yes, you don't have to have addon and subdomains in public_html folder for the document root. If your hosting provider allows subdomains and addon domains outside of public_html, when you fill out the folder for the addon or subdomain, remove the public_html portion. This will place it into /home/username/subdomainfolder path instead. Since the folder is outside public_html, it cannot be reached using http://maindomain.com/subdomainfolder any longer.