Use Clean up zone only after reviewing a domain that is intended solely for parking or forwarding. This action removes selected service and mail records; it is not a general repair for DNS problems.

Check whether cleanup is appropriate

Confirm that the domain does not rely on local website services or mail records that the cleanup targets. Keep a current snapshot and compare the complete record list with the intended configuration before proceeding.

The released cleanup targets service-host address/alias records and mail-related patterns, including apex MX, SPF and DKIM. Selection is based on record names/types/content patterns, not a reliable history of who added them. A matching record can matter even if a person created it deliberately.

Review and inspect the result

1. Open cPanel DNS → Zones and identify the exact forward-only domain.
2. Review current website, mail, verification and delegation requirements.
3. Read the Clean up zone confirmation carefully.
4. Use the action only if its removals match the intended service plan.
5. Inspect actual remaining records and verify required web/mail behaviour.

The workflow aims to leave authority information and the basic forwarding destination in place, but individual removals are performed separately. A result can reflect partial cleanup; read back the zone rather than assuming every intended change succeeded together.

Preserve useful DNS

Do not use this action on a domain with real local hosting or mail simply because its default-looking records seem unnecessary. Do not infer that every human-added record is automatically protected from the matching rules.

If the intended removals are unclear, preserve the snapshot and review the plan with the administrator responsible for the domain’s website, mail and DNS before running cleanup. For an ordinary single-record change use the relevant record guide instead.

Check the records to keep

Your hosting team should decide whether the domain is truly forward-only and review the full current records against the website, mail and verification services you intend to keep. If the intended removals are unclear, keep the snapshot and ask the administrator responsible for those services to review the plan before running cleanup. Record-name/type matching is not proof that a record is expendable or human-added records are protected. After a partial cleanup, read the actual remaining DNS before any further write.

See the PD cPanel DNS WHMCS guide for related tasks, or explore the module.