Enable the service you intend to operate under Service controls. Configure its supported runtime or forwarding backend, clusters and DNS arrangement. A DNS record alone cannot send an HTTP redirect or process an email message.

1. Open Email & Domain Forwarding and review Forwarding settings and Forwarding clusters.
2. Configure the appropriate web or mail backend and test connectivity.
3. Use Services by TLD and the relevant customer or reseller policies to define eligibility.
4. Test a controlled domain's ownership and nameserver preparation before enabling customer rules.
5. Verify a complete web redirect and an email delivery separately, including any destination-confirmation step.

For domain forwarding, decide which sources and path options are allowed and what redirect types your support documentation recommends. Temporary redirects are useful while testing; permanent redirects can remain cached after a rule changes.

For email forwarding, decide destination verification and catch-all policy. A forwarding address is not a mailbox with storage or an SMTP sending account. Explain how customers should receive mail at the destination and arrange outbound email separately.

The Ownership review workflow can review exact legacy cPanel rule matches. Adoption records the verified association without taking over unrelated panel rules or proving message delivery. Pause competing deployment processes while reviewing a domain so the comparison remains meaningful.

Do not import every rule in a shared panel account into the first matching customer. Confirm domain ownership and the exact remote rule before establishing module control.

A saved rule can remain pending until ownership, DNS or destination requirements are met. Follow its deployment status, then test the public URL or send a real test message from an unrelated mailbox. Check apex and www separately for web redirects.

If the domain uses another authoritative DNS provider, update the required records or delegation through a planned change. Preserve external mail and website records that the forwarding service is not meant to replace. For failures, compare rule status, public DNS and backend logs instead of repeatedly recreating the rule.

• Create a website redirect with Domain Forwarders
• Create and verify an email forwarder for your domain
• Add a DNS provider connection and prove that it can manage zones
• Review customer DNSSEC and reverse DNS requests