Move DNS off a cPanel DNS cluster to an AdminBolt hub. Your customers keep the nameserver names they use today.
Your servers can run different panels. Your customers see one set of nameservers.
Zones from your cPanel, DirectAdmin, Plesk and AdminBolt servers are answered under the same nameserver names.
Use the names your customers already have, such as ns1.provider.example. Their domains stay delegated to those names.
AdminBolt servers answer for your domains. Once they do, the WHM DNS cluster and its DNSOnly servers can be retired.
Your servers keep hosting sites and editing zones the way they do today.
Your servers keep hosting the sites. Zones are still edited on each server.
A supported record added or a zone deleted on a connected server reaches your AdminBolt nameservers. You can also start an update yourself.
You decide which AdminBolt server answers under each of your nameserver names.
Nothing moves off your cPanel servers. The servers that answer DNS change.
Switch on hub mode on a standalone AdminBolt server. It keeps hosting its own accounts.
Enable the DNS cluster with the nameserver names your customers already use.
Connect one AdminBolt server per nameserver name and give it the Secondary DNS role.
Give the hub administrative access to each cPanel server. It only reads the DNS zones there.
Check that the new nameservers answer for every zone. Point your nameserver names at them. Retire the WHM DNS cluster once the old addresses are no longer used.
Three things to plan for. The guide covers each of them.
The hub copies A, AAAA, CNAME, NS, MX, PTR, TXT and SRV records from cPanel. Other types such as CAA are not copied.
DNSSEC signatures are not copied. Remove the DS record of a signed domain at the registrar and wait for it to expire from caches before the switch.
When you move an account into AdminBolt, make the AdminBolt copy of its zone the one that is served until the cPanel server no longer has it.
The hub also manages your AdminBolt servers.
Resources and service status of your AdminBolt servers in one view.
Browse and suspend accounts on your AdminBolt servers. Move an account from one AdminBolt server to another.
The hub works with the servers and access you already have.
A standalone AdminBolt server, fully updated to 1.9.3 or later. It can host accounts of its own.
One fully updated AdminBolt server for each nameserver name, with its Secondary DNS role confirmed.
Administrative access to each cPanel server. Registrar access for signed domains and for nameserver names that get new addresses.
Read the guide, or tell us how your DNS runs today.