DNS Server Nodes

Watch the video tutorial

By default, DNS services are provided by the management node. It acts as a master DNS server for all zones registered in the system. Setup of DNS zones for newly added domains is automated: When a customer adds a new domain in the Hosting Panel, PPA automatically generates its zone file and registers it in the name server's database. You can view a list of domains registered in the system in Services > DNS Zones.

The functions of a master DNS server can be delegated to any node with the DNS role. You can also add slave DNS server nodes (slave servers periodically load zone data from the master server) or even more master DNS server nodes. In the latter case, PPA will create and update the same zone files on all master servers. Note that the DNS service does not require any provisioning attributes - the DNS service is an essential part of any service plan (service template) and is represented as a DNS resource type in the system. Learn more about how to work with DNS servers and the DNS resource in the Parallels Plesk Automation: Operations Guide, section DNS.

When you assign the DNS role to a node, the system automatically installs the BIND DNS server to that node.

Important: DNS servers do not require a license key. You can register any number of DNS servers in the system without any limitations.

Server Requirements

Before adding a DNS node to the environment, make sure that the server meets the following requirements.

OS

RHEL 5.9, 6.4 (32-bit or 64-bit)

CentOS 5.9, 6.4 (32-bit or 64-bit)

CloudLinux 6 (32-bit or 64-bit)

CPU

1 GHz or higher

RAM

1 GB minimum

Disk space

At least 1 GB free

Open TCP ports

DNS service: UDP port 53

Communication between a service node and PPA panels: TCP ports 8352-8999

Communication through SSH: TCP port 22

Adding a Node

To register a DNS server node in PPA:

  1. Add a DNS server node to the system by starting the Add New Node wizard in Administration Panel > Infrastructure > Service Nodes. The wizard will ask you to provide the following information:
  2. Normally, when the installation is complete, the node is marked as Ready to provide its services. If this does not happen, resolve the issue and mark it manually on the node properties page (Infrastructure > Service Nodes).
  3. Set this node as a master or slave name server in the DNS resource type properties located at the Products > Resources > DNS > Activation Parameters tab.
    In addition, you can set the SOA record template parameters: refresh and retry intervals, expiration period, and minimum TTL. The template settings are applied to the SOA record of all zones but can be overridden for a specific zone. Learn how to do this in the Parallels Plesk Automation: Operations Guide, section Managing DNS Zones.

    Note: You can set up to three name servers in the DNS resource type properties. The first name server is always master (by default, this is the management node).

 

Leave your comments on this page