• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Why a crazy subdomains schema?

jukar

New Pleskian
I wonder the reason for this anarchic schemo for subdomains.
I think it is very dificult to understand and to managment a site.
A subdomain IS NOT a domain, so it would be inside the domain structure (as in plesk 9)
But in 10.4 a subdomain is like a domain and like a subdomain.
Like a domain: it is in main folder and like a subdomain the folder root is inside folder of main domain.

I think this way is very crazy
If the idea is to consider subdomains as domains :
maindomain.com---- (httpdocs, cgi-bin, httpsdocs, ...)
subdomian1.maindomain.com: (httpdocs, cgi-bin, httpsdocs, ...)
subdomian2.maindomain.com: (httpdocs, cgi-bin, httpsdocs, ...)

And each one with a separate FTP access, so webmastres could access cgi.bin and errordocs...
but now it is a mix of the two options, and "webmasters of subdomains" cannot acces to cgi-bin via FTP.
Crazy.
Plesk does go in a bad way.
 
The concept of subdomains was revised to embody the following improvements:

- The support for own DNS zones.
- The support of Web Presence Builder for subdomains.
- Web hosting management tools (that change php.ini, vhost.conf, etc) are now available for subdomains.
- All domain-management features are available for subdomains.
- System files of subdomains are located in /vhosts/<subdomain-name>.example.com/ now, just like for a regular domain.
- All limitations on putting subdomains in the subdomains/ directory were eliminated.
 
But a little crazy

I understand the new features and the lost of old features.
Now subdomains are about like domains, ok, but they are managed by the owner of the main domain, they have not a user who can manage ONLY a subdomain. So what we have is a mixture of domains and subdomains, and it's a little tricky. Why can the httpdocs (the content of subdomains) be in any folder EXCEPT the subdomain.maindomain.com folder? If subdomains are like domains, the file structure would be like a domain structure.
And why SUBDOMAINS FOLDER inside subdomain.maindomain.com?

But subdomains are subdomains and domains are domains, I can't imagine why convert subdomains to this strange "domains".

I made a very bad choice when I updated to plesk 10!!!!

Thanks
 
Back
Top