Search Engine: Elastic

Article ID: 128805, created on May 6, 2016, last review on May 6, 2016

  • Applies to:
  • Plesk Automation 11.5


Branding NS are not applied to DNS zones owned by admin, there are still DNS service nodes host names instead of branding name servers. As a result branding DNS zone does not have branding name servers too.


Such behaviour is considered to be a software issue PPA-3308.


The issue is planned to be fixed in one of the future updates. As a workaround rename the DNS service nodes so they would have the same names as branding name servers.

For example, DNS service nodes have names ns1.isp.tld and ns2.isp.tld, and branding domain is So the desired branding name servers would be and

In this case the steps should be as follows:

  1. Go to System > Brands and clear Branded DNS Nameservers
  2. Add A records pointing to and server's IP to the zone  A  A
  3. Change the host names of the DNS service nodes in the OS:

    3.1. Run the hostname command:

    # hostname

    3.2. Open /etc/sysconfig/network, update the HOSTNAME line and save:

    # vim /etc/sysconfig/network

    3.3. Open your hosts file, and update the hostname entry and save:

    # vim /etc/hosts
  4. Update PA with the new hostnames using ppa.hostname --update utility (see the documentation below for the details):

  5. Check if activation parameters of the DNS resource and service templates have correct name servers.
  6. Update name servers for existing DNS zones by switching their type to External and back to Internal in the zones properties.

These steps will allow you to use desired name servers without setting up branding NS, so these name servers will be applied to all zones. The branding itself will not be affected and will work without issues.

33a70544d00d562bbc5b17762c4ed2b3 caea8340e2d186a540518d08602aa065 e0aff7830fa22f92062ee4db78133079

Email subscription for changes to this article
Save as PDF