A VPS with Plesk 11.5 was successfully provisioned via POA and a customer added a domain in the Plesk server using the POA Customer Control Panel. As a result, the following occurs:
The domain in POA Customer Control Panel has the status 'Failed to Add'.
The domain is suspended in Plesk.
In the POA debug poa.debug.log, the following error message appears when provisioning the domain to Plesk:
'DNS service is not enabled'
The POA Service Template used to create the VPS with Plesk 11.5 lacks the 'Bind' application template, so there is no DNS service in Plesk.
To fix the issue on a particular provisioned container, do the following:
Log in to the Plesk container via SSH as root.
Install 'bind' using the Plesk autoinstaller:
Turn off "Power User Mode" in Plesk Panel:
Log in to the Plesk Panel GUI and activate the problem domain(s).
Go to the "DNS Settings" page of the domain in Plesk Panel and restore them.
- In the POA Customer CP, go to 'Hosted Domains', find the needed domain, click on it, and then click the 'Resubmit to Parallels Plesk Panel' button.
To fix the issue globally (for all Plesk containers, including those that will be provisioned in the future), modify the Service Template in POA - add the 'Bind' application template to it.
Refer to the following Parallels Knowledgebase article for more details and best practices in creating Service Templates with Plesk in POA: #113489 How to create a service template for PVC containers with Parallels Plesk Panel provisioning