Prepare the domain’s account relationship before adding website or email forwarding in PD cPanel DNS. A DNS zone by itself is not the same as a domain attached to an account that can serve redirects or mail forwarding.

Identify the domain’s server account

Open cPanel DNS → Providers and confirm the intended WHM server. Ask its administrator whether the domain belongs to a real cPanel account or needs a prepared fallback account for forwarding-only use.

A fallback account must have the appropriate parked/aliased-domain allowance and the permissions required for attachment. Ordinary DNS-only privileges may not authorise that account-level route. Have the administrator approve the arrangement for the intended features; do not grant unrestricted access just to bypass an unexplained error.

Prepare and check before creating

1. Confirm the intended domain, existing provider zone and account owner.
2. Review the available fallback-account settings with the WHM administrator.
3. Check account domain limits and the permissions required by the chosen route.
4. Confirm DNS points website or mail traffic at the intended serving infrastructure.
5. Add a forward only after the ownership and service arrangement is ready.

If an existing DNS-only zone blocks attachment, retain the exact result and ask the administrator to reconcile it. Do not delete the zone or edit ownership data as a guessed repair. A domain already owned elsewhere must not be reassigned casually.

Check the required service separately

A redirect needs a serving web host and appropriate HTTPS certificate for secure source visits. Email forwarding needs mail to reach the intended mail server. The module does not supply free SSL or a new mailbox simply by creating a rule.

Use the website redirect guide or single-address email guide for the next task. Before removing the final forwarding rule, review the fallback attachment and DNS implications.

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