Innovate | Connect | Transform
ContactService statusUSD $

GICT knowledge base

Manage cPanel Domains, Aliases and Document Roots Safely

Published

cPanel

Current cPanel brings hosted domain names into the Domains interface. Older Addon Domains, Subdomains and Aliases screens may appear in historical guides, but this interface is not unrestricted server administration and does not register or renew domain ownership.

Choose separate content or an alias

Open verified HTTPS cPanel, then Domains > Create a New Domain. Enter the intended registered name or subdomain, following the installed version’s type choices. A separate website needs its own approved document root; sharing the main root serves the same content. Review that choice before creation because the share setting is not a casual toggle afterward.

Inspect generated fields and account limits before submitting. Separate FTP access, where needed, is configured through the account’s supported FTP controls with a unique credential and narrow path, not assumed from an old creation checkbox.

Use the domain list deliberately

The list identifies the main domain, document roots, redirects and available actions. A root link can open File Manager where permitted; mail creation, redirects and Zone Editor are separate supported controls. Site-builder tools and available shortcuts depend on release, plan and enabled features. The panel does not expose every user, DNS or system operation from one screen.

Manage can offer eligible document-root changes. It changes the lookup location, not the files themselves. The main domain and domains sharing its root have additional restrictions. See the main-root planning guide rather than editing server files blindly.

Keep DNS and redirects distinct

Use Zone Editor only when that zone is publicly authoritative, otherwise update the external provider. A/AAAA contain addresses, CNAME aliases a name and MX points to mail hosts; see the record reference. DNS publication does not create a working website or mailbox.

Use the cPanel Redirects guide for source paths, destinations, status and wildcard scope. For HTTPS enforcement, validate certificates first and use the supported toggle.

Remove a hosted domain without confusing data retention

Preserve a recoverable account before-state. Select only the intended eligible domain, use Remove Domain and review confirmation; the main domain cannot be removed here. Current documentation distinguishes removed web/DNS entries from retained directories and mail folders. Retained files are not a verified backup or proof all services remain usable. Review dependent applications, mail and external DNS separately before any later cleanup.

References: Domains overview and management and removal scope.

Reviewed October 16, 2026. The overlapping interface overview was consolidated here. No hosting account, domain or stored data was changed.

Related guides

Account services are unavailable until the production backend is configured.