The server hostname identifies WHM and other system services and can appear in mail headers. Change it through the supported cPanel workflow so dependent service configuration is updated consistently.
IN THIS ARTICLE
Prepare for the change
Choose a valid fully qualified hostname under a domain you control, distinct from customer account domains and reserved service names. Record the old hostname, DNS, reverse-DNS arrangement, certificates and integrations using it.
01 Change a WHM server hostname with DNS and certificate checks
- Publish or prepare an authoritative A record for the new hostname pointing to the server’s main IP, with appropriate IPv6 handling if used.
- Open Change Hostname in WHM and enter the reviewed new name. Complete the change and wait for required service updates.
- Use the offered A-entry action where the local DNS service is authoritative, and separately verify external authoritative DNS when it is hosted elsewhere.
- Review hostname certificate issuance and service certificates. Ask the IP provider to update reverse DNS where the mail-server identity requires it.
- Update monitoring, backup destinations, API endpoints and external-authentication redirect URLs that contain the old hostname. Test new WHM and mail connections.
02 Example: record one consistent server identity
Suppose the approved new hostname is server.example.com. This is an example beneath a domain you control, not a name to copy into a real server.
| Item to record | Expected relationship |
|---|---|
| WHM server hostname | server.example.com, used as the distinct server identity. |
| Authoritative A record | The hostname points to the actual main IPv4 address assigned to that server. |
| Service certificate | The certificate presented for the service covers the hostname clients will use. |
| Monitoring and integrations | Saved endpoints using the old name are reviewed and changed where required. |
Check any IPv6 record and reverse-DNS arrangement separately. A customer website should continue using its own website domain. Record the old values alongside the new ones so an incomplete transition can be diagnosed quickly.
Confirm the expected result
The new hostname should resolve correctly and present valid certificates for its intended services. Customer websites should retain their own domain names and continue operating.
If the change does not work
Changing only the operating-system hostname file can leave cPanel-managed services inconsistent. Cloud-provider metadata may also reapply a hostname unless configured through its supported process. Keep the old endpoint transition deliberate instead of abruptly removing every reference.
Should the hostname be a customer’s main website domain?
Use a distinct server identity, such as a dedicated hostname beneath a domain you control. cPanel advises against using a hostname that a hosted cPanel account will use.