Why doesn’t a new subdomain open after you create it?

Creating a subdomain usually requires both DNS and server configuration. Add an A, AAAA, or CNAME record for the new hostname, then add that hostname to the hosting platform or web server. If only one side is configured, the name may not resolve or the server may display a default site.

Confirm the document root and make sure it contains an index file or a working application. A subdomain can point to a separate folder, another server, or an external service. Check for typing differences between the DNS record, hosting entry, and URL, including duplicated domain names in panels that append the zone automatically.

Issue an SSL certificate that includes the subdomain before forcing HTTPS. A wildcard certificate can cover many first-level subdomains, but it has its own validation and scope rules. CDN or proxy services may also need the hostname added to their configuration before they will forward traffic.

Query the authoritative DNS record and inspect the HTTP response from the destination address. Allow valid DNS caches to expire after a recent change. Once DNS is correct, leave the record in place and review the server’s virtual host, application URL, file permissions, firewall, and logs.