A CNAME makes one hostname an alias of another hostname. It is useful for services that supply a canonical target, but it is not an HTTP redirect and does not change the URL displayed in a visitor’s browser.
IN THIS ARTICLE
Check access and requirements
Confirm cPanel serves the domain’s authoritative DNS and copy the exact target supplied by the destination service. A CNAME normally cannot coexist with other ordinary record types at the same name, and the zone apex has special constraints.
01 Add a CNAME record in cPanel
- Open Zone Editor and select Manage for the domain or use the CNAME shortcut.
- Enter the alias hostname, such as
shop.example.com. Review the final name after the panel expands any relative label. - Enter the target hostname without
https://, a port, or a URL path. Do not enter an IP address in the CNAME target field. - Resolve any conflicting record at the same name only after recording its existing purpose. Save the new CNAME.
- Complete the destination service’s custom-domain verification and certificate setup, then check DNS and the application over HTTPS.
02 Example: enter a CNAME target without URL components
If your service gives you an alias target such as tenant.platform.example, map it into cPanel Zone Editor as a hostname. This fictional target illustrates the required format. Use the exact current value issued by your destination service.
Name: shop.example.com.
Type: CNAME
TTL: 300
Target: tenant.platform.example.
Verification:
dig shop.example.com CNAME +noall +answerRead the result: The target contains no https:// prefix, port number, slash or website path. The resulting DNS answer should show shop.example.com as an alias of the supplied hostname. A CNAME does not send a browser to a different URL and does not enable a custom domain inside the destination platform.
Check for existing A, AAAA, TXT or other conflicting data at this exact alias name before changing it. Complete the provider's domain verification and certificate steps, then test the public HTTPS site. Leave apex and email records intact unless the migration specifically requires them.
Confirm the expected result
The alias should resolve through the intended target and the external service should recognise your hostname. DNS alone does not authorise an unknown domain on the destination application.
Why is the CNAME rejected, and can it replace a browser redirect?
If the panel rejects the record, inspect A, AAAA, MX or other conflicting records and confirm the hostname is appropriate for a CNAME. Do not replace the apex with a conventional CNAME unless the DNS provider explicitly supports an appropriate alternative. Use a web redirect when the browser URL must change.