cPanel & WHM Version 92 has been released, and brings a slew of great updates. Take a look at what is included, and then upgrade today!

True Multi Domain Support (Multiple Certificates & IPs per Acct)

Nathan Lierbo shared this idea 8 years ago
Open Discussion

The goal of the paradigm of True Multi-Domain Support is to eliminate the concept of a "main domain" along with the concept of "addon domains." Instead, the True Multi-Domain paradigm is of a hosting account that can have several domains, all having equal capabilities.

In the True Multi-Domain Paradigm:


  • Any domain can be parked on any other domain in an account
  • Adding a domain DOES NOT also result in a subdomain being created (negating all of the DNS and Apache overhead that comes with adding a subdomain)
  • Any domain can be assigned a static IP address
  • Because any domain can be assigned a static IP, multiple IP addresses and multiple SSLs can exist in a single hosting account

Implicit in this request is the ability to change the docroot of a domain without having to remove/re-add the domain. Multiple domains should be permitted to serve content from the same docroot.

Comments (16)

photo
2

I want to re-itterate my support for this feature request.


I'm unable to vote so I'm adding my +1 using the old way :)

photo
1

Isn't this in pre-release as I think the IPv6 support adds multiple IP addresses per account and the ability to choose the folder for the main domain is marked as planned… ? What about 1 ssl per IP ?

photo
5

This is something that has been needed and we've been asking for, for the last 10 years.


It's ridiculous that cPanel still creates sub-domains to park domains on top of for addon domains and you have to "hack" the userdata files to support multiple IPs/SSL per account. HSphere had multiple domain support right 10+ years ago.

photo
1

Yes, this has been requested, and have been a subject of threads around there many times, and no move from cPanel. Which would be the issue with improving the way domains are managed cPanel?

Please, rethink these stuff, and provide us a positive feedback you'll improve it.

When can we expct it to be done?

Thanks,

photo
1

Because cPanel links the main bad domain with a host of good domains.... resulting in making 100 good domains bad.... destroying their SEO.


cPanel needs to end this bad practice of linking domains, via auto creation of subdomains to main domain, because using cPanel is bad for SEO in the current setup.


None of the other panels or competitors of cPanel create subdomain link to main domain. This is a loss of business to cPanel hosts.

photo
1

I've been asking for this for years and am astounded that there's so few votes, as I've seen hundreds of complaints regarding this in many web forums.

photo
1

Unfortunately, its not something that only involves cPanel. The technology behind SNI was implemented in web servers just out of necessity. While email protocols (POP/IMAP) completely ignore the certificate name and accept even invalid ones. I've read a discussion by a dovecot developer, who was very opposed to implementing SNI just because its of no personal use to him. The same issue arises with others (ftp daemons, etc).


I really wish everyone got together and agreed upon a single SNI method that was used across all daemons, but it is hard to impose this across so many open source projects (small or large).


Essentially, if this was ever implemented across the board, then cPanel would essentially have its job done.

photo
1

This doesn't really have anything to do with SNI, although SNI is pretty well supported, I think there's only FTP and cPanel itself lacking SNI support now.


This is about getting cPanel to fix the mess of sub-domains with domains parked on them etc. This can be fixed regardless of SNI support and should have been dealt with years ago (I'm not saying anything I've not said directly to them).

photo
1

I partly agree, yes SNI should have been here a long time ago, but it was only recently (2015 I think?) that it was included to cover services other than HTTP.


But, I do insist that this is not a cPanel issue only, because it requires EVERY SINGLE client to support SNI as well, which pretty much covers loads of software (both closed source and open source).


About ftp in particular, maybe its just me but I haven't seen anyone use ftp in recent decades, most people use email for small file sizes (<25MB unencoded, <50MB encoded) and anyone sharing larger files they use HTTP instead. Maybe people also use free services like "wetransfer" which allow you to share up to 2GB files and others use a free online "harddrive". It seems like the technology in the FTP protocol is slowly dying.


Personally, I've got it disabled in all my servers and nobody has complained in a decade. Plus, most non-technical users don't even know what FTP is.


Anyway, back on topic, I hope that SNI is pushed everywhere eventually.

photo
2

As I said, this isn't about SNI, this is about getting rid of the mess of domains being parked on sub-domains and calling it "multi-domain", which should have been dealt with a long time ago instead of becoming so embeded.

Nothing in this request relies on SNI.

photo
1

I started a discussion on the forums and it was suggested to add my vote here: https://forums.cpanel.net/threads/the-age-old-add-on-domain-sub-domain-conflict.591127/


Would love to see the term "Primary" domain just dissappear forever.

photo
1

totally sign this.

this is the feature i wanted always most.. away from that one maindomain thing to have a real multidomain system.

every time a client give up his maindomain its a mess when he keeps the other projects.


its also such a mess when you want to add an alias domain to an existing addon domain, you have to create another addon which points to another addon.. this is nonsense.


this would also solve the issue, that you can update your maindomain project and just change the doc_root afterwards to the new page. This is currently not possible with that messy maindomain system.


so it should be something like..


public_html

- domain1 (docroot for domain1)

- domain2 (docroot for domain2)


basically the addon domain system, but the difference is, that your maindomain also gets set up like an addon domain instead of being the docroot of public_html

photo
1

Today I discovered this problem.. I have three domains on a single shared hosting account.. And saw this second-site.first-site.com to be working.. I mean what is this stuff.. Why on earth would you link two totally unrelated sites in this ugly manner citing technology constraints excuses when Humans have a reach till mars.. I dont understand why they cant overcome this problem.. Whats holding them back.. Moreover I see requests upto 4 years old and ppl wanting this to happen since 10 years.. One - Its bad for SEO.. Two - you dont want any connections or links betwwen two sites.. Three - You dont want people to relate between two sites. Four- you simply dont want the mess in Cpanel.. Five - if you want someone else like a trusted developer to login into your Cpanel, you dont want to show other projects.. And the list goes on and on and on.. This is simply unacceptable..

photo
1

My submission, which was similar to this, and which was gaining traction, was wiped out. Instead of rethinking everything, I just liked this one. However, I encourage any developer that might be looking into this, to look into this forum thread, which generated an approved feature request:

https://forums.cpanel.net/threads/assign-ip-address-to-subdomain.612807/

photo
1

I run an image hosting site; using a separate subdomain IP for every alternate thumbnail *HALVES* page load time for many users, because the browser will open multiple connections to different IP addresses. Ah well, maybe a workaround is a separate account and a separate TLD, and take the dns performance hit.