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

Question Cannot create Subdomains/DNS Zone on domains like <id>.web.mydomain.com

BenjaminK

New Pleskian
Hello everyone,

I'm currently facing a problem to provide webspaces for my customers.

In general, a unique domain is generated for each webspace with the following schema: <id>.web.mydomain.com.
If then users try to create sub domains like test.<id>.mydomain.com on this given domain, this error occurs: "Cannot create the DNS zone because its superzone belongs to another user." (translated from German).

I've read that you could disable this feature, but this approach would expose severe security problems.
Therefore, I really want to avoid it.

I'm not sure if the error really belongs to the domain names, but it's the most likely cause.
Is there any way of handling this, or do I really have to disable the feature?

There are some basic information about the plesk instance:
Code:
<version>
    <plesk_name>psa</plesk_name>
    <plesk_version>18.0.32</plesk_version>
    <plesk_os>Debian</plesk_os>
    <plesk_os_version>10.0</plesk_os_version>
    <plesk_build>1800201221.13</plesk_build>
    <os_release>4.19.0-10-amd64</os_release>
</version>

Many thanks in advance and a good evening
Benjamin K.
 
Back
Top