How to Set Up Clustered DNS With cPanel DNSONLY


  • If you rely on a DNS service running on your web server, every query must go to this server, meaning the queries will be slower for geographically remote users.
  • Outages on your web server will affect DNS resolution which is used for other functions, e.g email delivery. If your web server and DNS are hosted together, and your web server goes down for a few minutes, mail to that domain will be returned to the sending server’s queue and marked as a permanent failure. If the DNS service is clustered on separate servers, even if your web server goes down for a few minutes, the DNS server will still be running.
  • You could use a 3rd party DNS service like DNS Made Easy. However, you’ll have to manually update this 3rd party service each time you want to modify account details. cPanel will manage this for you by synchronising changes out to DNSONLY servers.


These steps apply if you have an existing cPanel WHM web server, and you want to create a DNS cluster, adding a new cPanel DNSOnly server.

  1. Obtain a new server, a hardware spec of 256mb memory, 10/15GB disk should be sufficient. Low End Talk sometimes have offers for this sort of server
  2. Install pre-requisites if necessary. On a fresh Centos 6.4 install, I needed:

yum install wget yum install perl

  1. Install cPanel DNSOnly:

cd /home wget -N sh latest-dnsonly

  1. Go to https://your_ip:2087/ and follow the wizard
  2. On your existing cPanel WHM server (the original web server):

    • Add your new server under clustering, set it to sync
    • Now follow these steps from the cPanel documentation
    • Set the server you’re adding to Synchronize Changes
    • Go to Edit DNS Zone and add a new NS record, pointing to the IP of the new DNS server
  3. On the new DNS server:

    • Go to WHM > Configure Cluster, check that the main server appears and the DNS role is Standalone. Generally it is not recommended setting up the DNS server to synchronize data to a web server

Check the Setup

  1. Log in to WHM on the main server and Synchronize one zone to all servers, with a test domain
  2. ssh into the dnsonly server, ls /var/named/*.com.db and you should see the synchronised account has been sent over
  3. You should also see the new zone on the ns3 server, from the Nameserver IPs page in the main server
  4. Check the report on intoDNS

Final Tweaks

  1. Install CSF; follow these steps. Configure as suggested here
    • You may need to use as the entry installation script.
    • You may need to edit the script to reduce the required memory on some hosts.
  2. Disable password access for ssh
  3. Disable httpd if installed
  4. Change the ssh port from the default
  5. Update SOA record defaults with DNS Functions > Edit Zone Templates:

    SOA Refresh: 1200 SOA Retry: 120 SOA Expire: 604800 SOA Min TTL: 3600


  • Error message “Requires version 8.9 or later”: add the IP of the dnsonly server to the cphulk whitelist on the web server. Also check for blocks and add to CSF rules. Then re-add the server to the cluster on the main web server

Further Reading