Know which two parts must work
A new subdomain needs both a hosting destination and a DNS record at the provider that serves the live zone.
A DirectAdmin subdomain configures a web destination for one hostname in the existing domain account. Creating blog.example.com in DirectAdmin prepares the hosting side if your account permits it. Visitors still need DNS for blog.example.com at the domain’s authoritative provider. DirectAdmin may add a record to its local zone, but that record has no public effect when another provider hosts DNS.
Before starting, check that the domain and DirectAdmin account are active and that the package permits subdomains. Choose a label that does not already host mail, an external application or another service. This article creates an ordinary web subdomain; it does not delegate a new DNS zone or add a domain pointer.
Record the existing site and destination
Write down the main site’s hostname, current web root and A/AAAA or CNAME answers. Decide whether the subdomain should serve its own files or point to an external provider. If the destination is an external application, that provider may require a CNAME or domain verification rather than a DirectAdmin web subdomain; use its instructions instead of creating an unused local web root.
For a DirectAdmin-hosted subdomain, make a backup of any existing directory or application using the intended label. Use dig NS example.com +short for an initial resolver view, then confirm the parent-zone delegation with dig +trace example.com NS or a direct query to an authoritative parent nameserver. If the answers differ, resolve that discrepancy before choosing where to edit live DNS. Note who can edit the live zone and whether DNS is proxied. The address to publish must be the one assigned for this website by the hosting provider, not an address copied from an unrelated DNS example.
Create the hosting-side subdomain
- Sign in at DirectAdmin User level, select the correct domain and open Sub-Domains Setup or its equivalent in your skin.
- Add the label, such as
blog, and confirm that DirectAdmin displays the full hostnameblog.example.com. Avoid entering the full name in a field that expects only the label. - Inspect the document root shown for the new subdomain. DirectAdmin versions and server configuration can place new subdomain files in different paths, and a document-root override may change it again. Do not assume it is a folder under the main site’s public directory.
- Place a harmless, temporary test page in the displayed root using the account’s approved file manager or deployment route. Avoid copying the main site’s configuration or credentials into a publicly served directory.
If the subdomain is absent from the panel or creation is denied, ask the host whether the account includes that feature. Do not attempt server-level changes from a customer account.
Publish DNS at the authoritative provider
Check whether the new hostname already has A, AAAA or CNAME records. If the DirectAdmin server is the destination, add only the address records the host has assigned. Publish an AAAA record only when the web service supports the assigned IPv6 address. If the provider instructed a CNAME to another hostname, do not keep an A or AAAA record at the same name. DNS panels vary in whether they expect blog or blog.example.com; inspect the final owner name before saving.
DirectAdmin’s local DNS record is sufficient only if its nameservers are authoritative for the domain. If the domain uses an external provider, copy the required record there and verify it publicly. Do not change nameservers merely to create a subdomain: doing so could affect the entire website and mail zone.
Test DNS, content and HTTPS separately
Query the hostname with dig blog.example.com A +short and, if IPv6 was configured, dig blog.example.com AAAA +short. Query an actual authoritative nameserver too if the public resolver still shows an old value. Visit http://blog.example.com/ and confirm the test page appears rather than the main site or a generic server page. Then request a certificate for the new hostname using the account’s available certificate workflow and test https://blog.example.com/. DNS resolution alone does not provide TLS.
Remove the temporary page after the intended application is installed. Check that example.com and www.example.com still serve the original site. If the subdomain resolves but shows the wrong content, inspect the configured document root and virtual host; if it does not resolve, check the authoritative DNS answer first.
For example, if blog.example.com resolves to the assigned address yet serves the main site, check the subdomain's root and host mapping. Confirm the response from the intended origin before changing live DNS again.
Recover from a wrong destination
If the new record points to the wrong service, restore the saved DNS value or remove only the new subdomain record. If the hosting-side subdomain uses the wrong document root, correct its setting before moving files. Deleting a DirectAdmin subdomain may remove or detach associated configuration; preserve files and confirm the panel’s deletion behaviour first. Cached DNS answers may persist for their earlier TTL after a correction.
When asking for help, provide the exact hostname, authoritative nameservers, intended hosting target, public DNS answer, document root shown in DirectAdmin and the HTTP/HTTPS result. Do not provide panel passwords.
Common questions
Why does it work inside DirectAdmin but not in a browser? The live DNS zone may be external or its record may still be cached.
Can I reuse the main site folder? A document-root override may allow it, but that intentionally serves the same files; check the security and routing consequences first.
Will the main site change? Adding a distinct hostname should leave its DNS and content alone; verify both after the change.
Sources and technical references
Related guides
Was this guide helpful?
If you accepted optional analytics, your Yes/No answer and this guide’s page address are sent to Google Analytics. No written feedback is collected. Read our privacy statement or change your choice in .
Need help with your service?
Open your client area or contact Novasean. Describe the symptom and checks you have performed. Keep passwords, recovery codes and private keys out of your message.