Quick answer
A subdomain needs both a DNS destination and a matching hosting/domain configuration. Creating one without the other can send visitors to a default page, the wrong site, or an invalid certificate.
Before you start
Choose the exact hostname, purpose, hosting account, and document root. Verify that the plan permits the additional site or subdomain and that its application requirements fit the account.
Steps
- In the authorized hosting control panel, create or confirm the subdomain mapping and the intended document root. Keep a staging or separate site in its own folder rather than mixing its files into production.
- At the authoritative DNS provider, add the approved A/AAAA or CNAME record for that hostname. Decide deliberately whether a supported web proxy should be enabled.
- Publish the reviewed files into the exact mapped root and ensure HTTPS covers the hostname through the provider's supported certificate workflow.
- Open the hostname as a visitor and verify the actual content, links, assets, redirects, and certificate. Check that the main domain remains unchanged.
Verify the result
DNS, hosting mapping, application base URL, and certificate should all refer to the same intended hostname. Record the document root for future deployments.
Troubleshooting and recovery
If you see another website, compare DNS and virtual-host mapping before uploading again. A certificate error should be repaired through the correct hostname/certificate configuration, not bypassed in the browser.
Related help
- Find what is using your hosting disk space
- Choose an A, AAAA or CNAME record for a website hostname
- Check and troubleshoot HTTPS certificates for your domain
Official references
Reviewed October 31, 2026. Interfaces, vendor availability, and account features can change. Check your current account before making changes.
