Confirm ownership of the new registered domain and back up the account. Inventory mail identities, certificates, DNS, application URLs, webhooks and links using the old name.

1. Open Modify an Account and select the intended account. Record the current primary domain and relevant service usernames.
2. Prepare authoritative DNS for the new name and decide whether the old domain must remain available as an alias or redirect. Avoid an existing domain collision on the server.
3. Change the Primary Domain field, or use the offered replacement action for an eligible temporary-domain account, then save.
4. Inspect the renamed service accounts and update external DNS, mail clients and application base URLs as required. Obtain valid HTTPS coverage for the new hostname.
5. Test the new site, login, forms, mail sending and receipt. Check old links through the deliberate alias or redirect plan.

The new domain should reach the intended website and services with valid certificates. The account’s stored files remain part of the existing account rather than being recreated from nothing.

If the new name fails, separate DNS, certificate and application-URL problems. Do not change the username simultaneously unless the maintenance plan covers both sets of dependencies. Reverse changes through supported controls and saved settings when necessary.

No. Register the new name if necessary, or confirm that you already control it through its current registrar. A registrar transfer is not required simply to change the hosting account’s primary domain. Manage renewals separately: changing hosting configuration does not cancel or renew either registration.

• Changing a cPanel username and reviewing its dependencies
• Renaming a domain in supported cPanel versions
• Reading AutoSSL logs for a domain-validation failure
• Changing an account bandwidth allowance in WHM

• cPanel: Modify An Account
• cPanel: Manage The Domain