Learn how to add a domain in DirectAdmin, including domain setup, DNS records, document roots, SSL, email and common setup checks.
Adding a domain in DirectAdmin creates a place for that domain to use website files, DNS records, SSL and email. The important part is knowing whether the domain should have its own website, point to an existing site, or simply redirect visitors somewhere else.
This guide explains the practical process: adding the domain inside DirectAdmin, checking the document root, pointing DNS correctly, installing SSL and testing the result. It is written for Website Hosts UK customers and anyone using DirectAdmin who wants to avoid the common mistakes that cause new domains to show the wrong page, fail SSL validation or break email.
Before changing anything, decide what the domain is meant to do. A brand-new website, a parked domain, a redirect and a second domain showing the same content are different setups. Choosing the right option at the start saves a lot of troubleshooting later.
Add the domain in DirectAdmin, point DNS to the correct server, upload files into the right document root, install SSL, then test both the website and email records.
Adding a domain in DirectAdmin tells the hosting account that the domain should be handled by that account. DirectAdmin can then create the website folder, DNS zone, SSL options, email options and related controls for that domain.
It does not automatically move the domain registration, transfer the website files, update external DNS or copy email from another provider. Those jobs may still need to be done separately depending on where the domain currently points.
Think of DirectAdmin as preparing the hosting space. The domain will only work publicly when DNS sends visitors to that hosting space and the right website files are in the right folder.
In DirectAdmin, go to Account Manager and choose Domain Setup. Select Add New, enter the domain name without https:// and without a trailing slash, then create the domain.
Use example.co.uk, not https://example.co.uk and not www.example.co.uk/. The www version is normally handled with DNS and SSL once the main domain is added.
After the domain is added, DirectAdmin should show it in the domain list. If the account has reached its domain limit, the add button may fail or the package may need adjusting before more domains can be added.
Not every domain should be added in the same way. The right choice depends on whether the domain needs a separate website, should show the same website as another domain, or should forward visitors elsewhere.
Use this when the domain needs its own website files, SSL and possibly its own email addresses.
Use this when another domain should show the same website, such as a .com and .co.uk version of the same brand.
Use this for sections such as shop.example.co.uk, blog.example.co.uk or portal.example.co.uk.
Use this when the domain should send visitors to another address rather than host its own website.
Once the domain exists in DirectAdmin, DNS needs to point the public internet to the correct server. If your domain uses Website Hosts UK nameservers, the DirectAdmin DNS zone can usually manage the records. If your domain uses external DNS, update the records wherever DNS is currently hosted.
The most important website record is usually the A record. It should point the domain to the server IP address for the hosting account. If you use IPv6, the AAAA record also needs to be correct. For the www version, use either a CNAME to the main domain or an A record pointing to the same server, depending on your setup.
| Record | What it controls | What to check |
|---|---|---|
| A record | Where the main domain loads from. | Check it points to the correct hosting server IP. |
| AAAA record | IPv6 version of the website address. | Remove or correct it if it points to an old server. |
| CNAME | Often used for www or service aliases. | Check www resolves to the intended domain. |
| MX records | Where incoming email is delivered. | Do not overwrite these if email is hosted elsewhere. |
| SPF, DKIM, DMARC | Email authentication and delivery trust. | Make sure they match the service sending your email. |
The document root is the folder DirectAdmin uses to serve the website. If files are uploaded into the wrong folder, the domain may show a default page, an empty directory, an old website or a completely different website.
For a normal domain, the website files usually need to sit in that domain's public_html area. Upload the homepage file, WordPress installation or website build into the correct domain folder rather than the first public_html folder you see.
This is especially important when one DirectAdmin account contains more than one domain. Always confirm the path before replacing files, because uploading into the wrong folder can overwrite another live website.
SSL should normally be installed after DNS points to the hosting account. If the domain still points elsewhere, Let's Encrypt validation may fail because the certificate system cannot confirm the domain reaches the correct server.
In DirectAdmin, open the SSL Certificates area for the domain and request a certificate for the main domain and the www version where needed. Once installed, test both https://example.co.uk and https://www.example.co.uk.
If SSL fails, check the A record, www record, domain pointer settings and any existing redirects. A redirect to another domain can sometimes block validation until the DNS and website setup are corrected.
Website DNS and email DNS are linked but separate. A domain can load its website from one host while email is handled by another provider. Before changing nameservers or replacing DNS records, check where the current MX records point.
If the business already uses Microsoft 365, Google Workspace or another external mail provider, copying only the website A record is safer than replacing the whole DNS zone. Otherwise, the website may start working while email suddenly stops receiving messages.
| Problem | Likely cause | Fix |
|---|---|---|
| Domain does not load | DNS still points to the old server or has not propagated. | Check the A record and nameservers, then allow time for propagation. |
| Default page appears | The domain reaches the server but real website files are missing. | Upload files into the correct document root and replace the default index file. |
| Wrong website appears | The domain is using the wrong folder, pointer or redirect. | Check Domain Setup, pointers, aliases and the document root. |
| SSL will not issue | DNS does not resolve to the DirectAdmin server yet. | Fix the DNS first, then retry Let's Encrypt after the domain resolves correctly. |
| Email stops working | MX records were changed or removed during the DNS update. | Restore the correct MX, SPF, DKIM and DMARC records for the mail provider. |
Most DirectAdmin domain setup issues come from mixing up the domain type, DNS provider or upload folder. These are the mistakes to watch for before making the domain live.
public_html folder.DirectAdmin makes it straightforward to add domains, but the order matters: add the domain, confirm DNS, upload to the right folder, install SSL, then test the website and email records.
You can start with DirectAdmin Hosting or manage domain registration through Domain Services.
If the domain is being moved from another provider, make a note of the old DNS records first so website and email services can be restored quickly if something does not behave as expected.
Log in to DirectAdmin, open Account Manager, choose Domain Setup, select Add New, enter the domain name without https:// or www, then create it. DirectAdmin will create the domain area and the folder structure for that domain.
An additional domain normally has its own website files, email options and domain area. A domain pointer is usually used to point another domain at an existing website, such as forwarding example.net to the same site as example.co.uk.
Only if the domain is not already using the hosting provider's DNS. If DNS is managed elsewhere, keep the existing nameservers and update the A, AAAA, MX and other records at the current DNS provider instead.
The DirectAdmin side is usually created straight away, but DNS changes can take time to update across networks. Some visitors may see the new site quickly while others may still see old records until propagation completes.
Upload the website files into the domain's document root, normally the public_html folder for that domain. Make sure you are inside the correct domain folder before replacing or uploading files.
A default page normally means the domain is reaching the server but the real website files are missing, in the wrong folder, or the default index file has not been replaced.
SSL usually fails when DNS does not point to the hosting account yet, the domain is still resolving elsewhere, the www record is missing, or there is an old redirect blocking validation.
Yes, if the hosting package includes email and the domain's mail records are configured correctly. You may also need MX, SPF, DKIM and DMARC records before sending and receiving works reliably.
Yes. Use a domain pointer or redirect when several domains should show the same website. Use a separate additional domain when each domain needs its own files, SSL and email setup.
Check the domain's website files, email accounts, databases, redirects and DNS first. Removing a domain can remove access to the website area and related services, so take a backup before deleting anything important.
Adding a domain in DirectAdmin is simple once you know what each part does. DirectAdmin creates the hosting space, DNS points visitors to it, the document root stores the files, SSL secures the connection and MX records control email delivery.
Work in that order and test each part before moving on. It is much easier to fix one missing A record or one wrong folder than to troubleshoot DNS, files, SSL and email all at the same time.
DirectAdmin Guides
Use these related guides to compare DirectAdmin hosting, pricing, demos, WordPress setup, email tools and cPanel alternatives.
Install for quick access to hosting, tools, billing and support.