Legacy MyDNS on cPanel: Review Before Replacing It

MyDNS/MyDNS-NG appears in historical cPanel instructions, but it is not a nameserver choice in the current WHM Nameserver Selection documentation. Do not install it or run old forced-import commands on a current cPanel server merely because an older screenshot lists it.

Why the old procedure needs replacement

The earlier guide described a database-backed MyDNS service, its per-server MySQL dependency, a forced import and a service restart. Those details belong to an older cPanel integration, not a supported current installation recipe. Old cPanel/MySQL minimum versions are not safe deployment requirements today. A responsive database alone also does not establish correct DNS answers.

If an existing server still uses MyDNS

1. Identify the exact cPanel, operating-system and nameserver versions and whether they remain supported. Preserve configuration, authoritative zone data and relevant database backups privately.
2. Inventory delegation, DNSSEC, cluster peers, local resolver dependencies and every zone that must remain available.
3. Plan a supported maintenance/upgrade path with the administrator or vendor. Do not mix a standalone replacement package with cPanel’s managed service.
4. Rehearse data conversion and recovery in isolation. Compare actual record sets and answers, not just zone counts or a successful import message.
5. Perform an approved cutover only after a rollback plan and external verification are ready.

Current nameserver selection

WHM documents PowerDNS, BIND where available for the operating system, or Disabled. See changing cPanel nameserver software for the review sequence. Disabling DNS is appropriate only when another documented authoritative design covers the zones; it is not a migration shortcut.

This page retains the historical MyDNS purpose and existing-system recovery context instead of presenting obsolete import/restart commands as current instructions. Use a support ticket if you cannot establish the server’s supported path; do not expose database credentials or backups.

Reference: current WHM Nameserver Selection.

Reviewed October 16, 2026. Documentation review only; no MyDNS deployment, import, upgrade or recovery was executed.