Create or identify the actual cPanel account that will own the aliases. Record its cPanel username, not its primary domain, WHM login or email address. Confirm that its website content, routing and certificate arrangements are suitable for the landing page you intend to display.

The WHM credential needs permissions for the operations you will perform. DNS management and creating a domain alias are separate capabilities. Restrict the token appropriately, including source addresses when available, and verify alias creation on a domain you control.

1. Open DNS Manager > Servers and edit the cPanel/WHM connection.
2. Enter the existing username in cPanel Account Username.
3. Save and test the connection, then create a controlled DNS-only domain through its package.
4. Verify that the alias belongs to the intended account and that the DNS records are preserved.
5. Check public delegation and web behaviour separately. An alias in cPanel does not make an unrelated public DNS service point to its landing page.

New eligible DNS-only domains can be created as aliases immediately. Existing eligible standalone zones are considered by a background migration, which runs on its scheduled cadence. The migration preserves records and skips domains that are already hosted, owned elsewhere, locked by work in progress or affected by unresolved drift.

Do not delete an existing hosted domain to make it fit this workflow. Investigate why the migration skipped it. A domain carrying a real website is not merely an unused DNS zone.

Clearing the optional username stops future owner-based parking. Changing it does not automatically transfer existing aliases from the previous cPanel account. Plan any ownership move separately and verify the actual cPanel state before promising customers a changed landing page.

If later provisioning creates a hosting account for the same domain, use the configured hosting-transition workflow. It checks owner and server relationships, preserves DNS and handles the alias conflict around WHMCS provisioning.

If alias creation fails, check the exact username, account existence, WHM token privileges and whether the domain already exists under another owner. If the alias exists but the page is wrong, inspect authoritative A/AAAA records, web routing and SSL for the domain rather than changing the DNS owner repeatedly.

• Add a DNS provider connection and prove that it can manage zones
• Preserve DNS when a parked domain becomes a hosting account
• Create DNS record sets that become package defaults
• Keep Domain Nexus jobs, scheduled DNS changes and reconciliation running

• cPanel: Manage API Tokens in WHM
• cPanel: Create domain alias