Choose and configure the nameserver service in WHM (PowerDNS or BIND)
Pick the right DNS service in WHM Nameserver Selection. Compare PowerDNS, BIND and disabled, decide when external DNS is better, switch safely and check zones still resolve.
- Intermediate
- Linux VPS
- 4 min read
cPanel can answer DNS queries for your hosted domains itself, using PowerDNS or BIND, or it can leave DNS to someone else. The choice is made in one WHM screen, but it affects every domain on the server. This guide explains the options, when each one fits and how to switch without taking sites offline.
Before you start
- Root access to WHM on a cPanel server running on a RunRacks Linux VPS.
- Know how your domains get DNS today: from your own nameservers on this server, or from an external DNS provider.
- A recent backup of your zone files. They live in
/var/named/on cPanel servers.
tar czf /root/zones-$(date +%F).tar.gz /var/named/*.dbThe options
Go to Home » Service Configuration » Nameserver Selection. You will see:
- PowerDNS. The default on current cPanel versions. It reads the same zone files cPanel manages and is light on memory. cPanel notes it does not work as a recursive nameserver, which is fine, because an authoritative server should not be a public resolver anyway.
- BIND. The traditional choice. It is not available on Ubuntu servers, where PowerDNS is the only supported option.
- Disabled. No DNS service runs on the server. cPanel still keeps zone files, so you can copy records to an external provider or to a DNS cluster.
cPanel recommends not running a nameserver at all unless you plan to use it.
When to use external DNS instead
Running DNS on a single VPS means DNS goes down whenever the server does. Choose Disabled and host DNS elsewhere if:
- your domains already use a DNS provider such as a registrar's DNS or a CDN;
- you want DNS to keep answering during server maintenance;
- you only host a few domains and do not need branded nameservers.
In that case, you add the records (A, MX, TXT and so on) at the external provider and keep cPanel's zone files as a reference.
Keep a local DNS service if:
- you offer hosting to customers who point their domains at your
ns1andns2; - you want AutoSSL and new accounts to work without editing DNS somewhere else.
Switch the nameserver service safely
Switching restarts DNS. For a few seconds the server will not answer queries. Do it at a quiet time and do not switch back and forth.
- Back up the zones as shown above.
- In Nameserver Selection, choose the new option and click Save.
- WHM installs or enables the selected service and stops the old one. Wait for the confirmation output to finish.
- Check the service is running:
systemctl status pdns --no-pagerOn a BIND server, the service is named:
systemctl status named --no-pagerIf you chose Disabled, confirm that nothing listens on port 53:
ss -lntup | grep ':53 'Check zones still resolve
Pick two or three hosted domains and query the server directly:
dig @203.0.113.10 example.com A +short
dig @203.0.113.10 example.com MX +short
dig @203.0.113.10 example.com SOA +shortEach should return the records you expect. Then check from outside:
dig example.com A +shortIf you disabled local DNS, the public answer must now come from your external provider. Check with dig example.com NS +short.
Troubleshooting
- PowerDNS fails to start: another program, often a local resolver such as
systemd-resolvedon some systems, holds port 53 on all addresses. Check withss -lntup | grep :53and stop the conflict. - Some zones return SERVFAIL after switching: a zone file has a syntax error the old server tolerated. Look at the service log with
journalctl -u pdnsand fix the zone in Home » DNS Functions » Zone Editor. - Domains stop resolving after choosing Disabled: their NS records still point at this server. Move them to the external provider at the registrar first.
- BIND is greyed out: the server runs Ubuntu. Use PowerDNS.
Next steps
- Brand your DNS: set up private nameservers with cPanel & WHM.
- Add redundancy: set up a WHM DNS cluster.
- Learn the record types: DNS records explained.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Control panels
How to install Plesk on a Linux VPS (AlmaLinux and Ubuntu)
Install Plesk on a fresh Linux VPS with the official one-click installer, apply your licence key and log in to the panel for the first time on port 8443.
- Beginner
- Linux VPS
- 8 min read
Control panels
CyberPanel: back up and restore a website
Create on-demand and scheduled website backups in CyberPanel, download the archives off the server, and restore a site from a backup when something breaks.
- Intermediate
- Linux VPS
- 6 min read
Control panels
Plesk Backup Manager: schedule backups and restore a site
Set up scheduled backups in Plesk Backup Manager, keep a copy off the server, and restore a single domain or subscription when something goes wrong.
- Intermediate
- Linux VPS
- 7 min read