Article ID: 117054, created on Sep 2, 2013, last review on Jun 17, 2016

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4
  • Plesk 11.5 for Linux


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:

  1. The domain in POA Customer Control Panel has the status 'Failed to Add'.

  2. The domain is suspended in Plesk.

  3. 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:

  1. Log in to the Plesk container via SSH as root.

  2. Install 'bind' using the Plesk autoinstaller:

  3. Turn off "Power User Mode" in Plesk Panel:

    /usr/local/psa/bin/poweruser --off
  4. Log in to the Plesk Panel GUI and activate the problem domain(s).

  5. Go to the "DNS Settings" page of the domain in Plesk Panel and restore them.

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

Search Words

how to change hosting type

dns service is not enabled

change Hosting type


failed to add

I cannot see power user panel

domain is suspended

a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c 01bc4c8cf5b7f01f815a7ada004154a2 29d1e90fd304f01e6420fbe60f66f838 0a53c5a9ca65a74d37ef5c5eaeb55d7f ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37 614fd0b754f34d5efe9627f2057b8642

Email subscription for changes to this article
Save as PDF