• 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.

Clarification of subdomain operation

C

Cylindric

Guest
Hi, we've just upgraded to a new VPS running Plesk 10.4.4 and I'm setting up my sites now.

So I have a Workspace called "mydomain.com", and I want several subdomains "test.mydomain.com" and "beta.mydomain.com".

I can create subdomains, and set the path to be /subdomains/test/httpdocs and /subdomains/test/beta/httpdocs and that works fine, but the directory structure created is like this:

/var/www/vhosts/mydomain.com/httpdocs <-- this is the main site httpdocs, fine
/var/www/vhosts/mydomain.com/subdomains/beta/httpdocs <-- this is the sub-site httpdocs, fine
/var/www/vhosts/mydomain.com/subdomains/test/httpdocs <-- this is the sub-site httpdocs, fine
/var/www/vhosts/test.intellectuk.org/... <-- what is this??

If I have to have all the subdomains in the root and the parent site's subdomains, what's the point? Or is it just a sales technique to get more licenses out of users?
 
That doesn't really answer my question. Do I need those /{subdomain} directories? Your document implies it's just for "backward compatibility" - not that I'm going to downgrade.

If I don't need them, where do all the logs go for subdomains?
 
Back
Top