Manage DNS Zones in WHM Without Losing Custom Records

WHM can create and manage DNS zones for authorized accounts. A local zone changes public DNS only if the domain’s authoritative service publishes it. Before editing, confirm the intended domain, account, provider and delegated nameservers; preserve the current zone privately.

Create a zone only when one is needed

Use verified HTTPS WHM and DNS Functions > Add a DNS Zone. Enter the intended IPv4 address and domain, associate the correct account when applicable, review and submit. If the domain already has a zone, manage that zone instead of trying to add another one. Account/domain creation can already have generated it.

A generated zone comes from a template. Review its website, mail, nameserver and verification records; a template is not evidence that every service is configured correctly. Creating a zone does not register a domain or change registrar delegation.

Edit or remove individual records

Use DNS Functions > DNS Zone Manager, locate the exact domain and choose Manage. Add, edit or delete the specific record, checking owner-name suffixes, type, value and TTL. The raw-zone view can help preserve a before-state. Old guides show the separate Edit DNS Zone screen and generated file comments; those comments are not additional DNS record types.

SOA holds zone metadata, NS identifies authoritative servers, A/AAAA contain addresses, MX contains a mail-hostname preference and CNAME creates an alias. See the record reference rather than treating these fields interchangeably.

Whole-zone deletion and reset are destructive

Use the installed Delete a DNS Zone interface only after confirming the exact zone and every dependent service. A removed local zone can also affect cluster peers according to the configuration. It does not unregister the domain or clear cached answers.

Zone Manager’s Actions > Reset DNS Zone removes custom records and recreates defaults. Preserve required records first; do not use reset as a routine fix for one broken entry or assume it restores an earlier backup. Cancel if the intended recovery state is unknown.

Verify the result

Inspect saved data, query each authoritative server, compare recursive responses and test the affected service separately. Review cluster publication and DNSSEC relationships where applicable. A green save notification or a changing SOA serial is not a complete public-service check. Use a support ticket for account-specific assistance; no universal administration entitlement is implied.

References: WHM zone creation and DNS Zone Manager.

Reviewed October 16, 2026 against vendor documentation. No live zone, account or DNS service was changed or tested.