Distinguish cPanel’s domain forwarder from a catch-all mailbox before using the domain-wide email control in PD cPanel DNS. Similar labels do not mean the underlying server operations accept the same destination.

Choose the intended mail behaviour

A single-address forward sends mail for one source address to a receiving address. A native cPanel domain forwarder sends undeliverable recipients to the corresponding recipient at another domain. Existing deliverable addresses or autoresponders can take precedence.

A catch-all mailbox instead collects unknown recipients into one chosen address. cPanel documents that separately under its Default Address interface. Its Forwarders guide explains the domain-forwarding distinction.

Check the module’s domain-wide control

The released cPanel adapter maps the shared catch-all operation to cPanel’s domain-forwarder API. The shared form’s Send all unmatched mail to wording must not be treated as proof that it configures a native Default Address mailbox.

Do not enter a mailbox into that field and assume it will deliver every unknown address there. Ask the cPanel administrator to confirm the intended native domain-forwarding route and destination type, or configure a mailbox catch-all through the supported Default Address workflow.

Verify the actual result

1. Identify whether the requirement is one alias, domain-to-domain forwarding or a single mailbox catch-all.
2. Confirm the source domain’s account and mail routing.
3. Review the existing native mail rules with the administrator.
4. Test both an existing address and an unknown recipient where appropriate.
5. Keep the exact redacted rule/result if behaviour differs from the intended route.

Saving a rule is not proof that MX routes mail to this server. Use the single-address guide for an ordinary alias, and avoid repeatedly adding conflicting domain rules to work around a destination mismatch.

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