DNS Management Settings
By default, CloudBlue Commerce does not synchronize domains and their zones created on CloudBlue Commerce DNS farm with Plesk and conversely. You can configure synchronization of DNS zones between CloudBlue Commerce and Plesk. On the scheme below you can see architectural changes when DNS zone synchronization is enabled.
Important: You must add DNS resource type based on DNS Hosting resource class to your VPS Hosting service template, otherwise synchronization of DNS zones won't work, even if you have chosen the option. To add DNS resource type, go to Products > Service Templates, click the name of your VPS Hosting service template, switch to Resources tab, click Add resources, find and select DNS, then click Submit. Plesk name servers act as Master, and name servers specified in resource type DNS act as Slave.
The Propagate DNS zones to CloudBlue Commerce slave NS nodes option is a global option, used to activate the synchronization of DNS zones between Plesk (master) and CloudBlue Commerce (slave) name servers. If the Propagate DNS zones to CloudBlue Commerce slave NS nodes option is disabled, synchronization won’t work and a customer won't be able to manage Plesk DNS zones via CCP (the respective functionality will be hidden in CCP).
Note: Be aware that change of the Propagate DNS zones to CloudBlue Commerce slave NS nodes option is applied only to the newly added domains and does not change configuration of the existing domains. PTR records are not propagated (this is a temporary limitation, which is going to be improved).
The Propagate DNS zones to CloudBlue Commerce slave NS nodes option should be used in combination with one of the options described below or both of them:
- Delegate CloudBlue Commerce DNS zones management to Plesk – to reset the existing CloudBlue Commerce DNS zones and use DNS records from Plesk DNS zones of the same domain name. In this case, Plesk acts as a master nameserver while CloudBlue Commerce NS nodes – as slave nameservers. This option is used when you have domains with the same name in both CloudBlue Commerce and Plesk. DNS zone synchronization is performed via the customer CP. For more details, refer to the Cloud Infrastructure Subscriber's Guide.
- Automatically create domains in CloudBlue Commerce on domain creation in Plesk – to automatically create DNS zone in CloudBlue Commerce and propagate Plesk DNS zone records to it. Existing domains with the same names in CloudBlue Commerce won't be changed. This option is used when you create a new domain in Plesk and there is no such domain in CloudBlue Commerce. Compared to the Delegate CloudBlue Commerce DNS zones management to Plesk option, the current one doesn't require manual actions in the customer CP or Plesk control panel to synchronize DNS zones.
The following combinations of these two options are possible:
|
Case |
Delegate CloudBlue Commerce DNS zones management to Plesk | Automatically create domains in CloudBlue Commerce on domain creation in Plesk |
Valid for the following customer scenarios |
|---|---|---|---|
|
Case 1 |
Enabled |
Disabled |
|
|
Case 2 |
Disabled |
Enabled |
Creating webspace in Plesk (the domain is not purchased in CloudBlue Commerce and not registered by the domain registrar) |
|
Case 3 |
Enabled |
Enabled |
All scenarios described above in this table |
Different combinations of these options will effect the availability of options related to DNS zone management in the customer CP. To learn more about DNS zone management in the CCP v1, refer to the Cloud Infrastructure Subscriber's Guide >> Managing VPS Hosting > Managing Plesk > Managing DNS Zones section. DNS zone management in the UX1 for Customers has the same logic.