HestiaCP: add a domain, DNS zone and mail domain
Create a web domain in HestiaCP and let the panel build the matching DNS zone and mail domain, then add a mailbox and point the domain at your server.
- Beginner
- Linux VPS
- 6 min read
When you add a domain in HestiaCP, the panel can create the web domain, the DNS zone and the mail domain in a single step. This guide walks through that form, the records HestiaCP writes for you, your first mailbox, and the registrar change that makes the site and mail reachable from the internet.
You need root or panel access to a Linux VPS with HestiaCP installed, plus a registered domain you control.
Before you start
- A Linux VPS running HestiaCP. The panel is usually reachable at
https://203.0.113.10:8083— use your server's public IP. - An admin account, or a normal user account. Admin can add domains to any user; a normal user can only add domains to their own account.
- Your domain registered and the registrar login ready. You will either change nameservers or copy a few records.
- DNS and Mail support switched on in the package assigned to the user. If either is off, the domain is created without a zone or without a mail domain.
- Optional: SSH access, for example
ssh [email protected], if you prefer the command line.
HestiaCP is community software that ships with your own VPS, and it is not sold by RunRacks. If a screen or field name differs from this article, check the panel's own documentation for your release.
Add the domain in HestiaCP
- Log in to the panel at
https://203.0.113.10:8083. - Open Web and choose Add Domain (newer builds use a + button above the domain list).
- Fill in the form:
- Domain:
example.com - IP address: your server's public IPv4 address
- Aliases:
www.example.com - Tick Create DNS zone and Create mail domain if those options are shown and you want them.
- Save. HestiaCP creates the document root at
/home/deploy/web/example.com/public_htmland reloads the web server.
The same thing from the shell:
/usr/local/hestia/bin/v-add-web-domain deploy example.com 203.0.113.10
/usr/local/hestia/bin/v-add-dns-domain deploy example.com 203.0.113.10
/usr/local/hestia/bin/v-add-mail-domain deploy example.comArgument order and flags change between panel releases. Run a script on its own, for example /usr/local/hestia/bin/v-add-web-domain, to see the usage line for your build, or stay in the web interface.
Upload your files to public_html over SFTP as the deploy user, or drop a test file there:
echo 'hello from example.com' | sudo -u deploy tee /home/deploy/web/example.com/public_html/index.htmlCheck the DNS zone HestiaCP created
Open DNS in the panel. You should see example.com with a set of records: A for the domain, A for mail, A for www, MX, and a TXT record carrying SPF. The zone file lives on disk under /home/deploy/conf/dns/. List what the panel holds:
/usr/local/hestia/bin/v-list-dns-records deploy example.comIf the mail domain has a DKIM key, copy the public key record into the zone as well — without it, receiving servers have no way to verify signatures from your server, and your mail is more likely to be filtered.
Deleting or rewriting records in a live zone can take the website or mail offline once caches expire. Add records rather than replacing them, and keep a copy of the working zone before you edit.
If your registrar or a third-party DNS provider hosts DNS for this domain instead, you can leave HestiaCP's zone in place. It simply will not be queried by anyone. Either way, you need the values from this screen — the server IP, the mail hostname, and the SPF and DKIM strings.
Create the mail domain and a mailbox
Open Mail. example.com should be listed as a mail domain because you ticked that option when adding the site. Open it and choose Add Account:
- Username:
deploy(the address becomes[email protected]) - Password: a long, unique password
- Quota: leave the default unless you have a reason to change it
Then send and receive mail with these settings:
IMAP mail.example.com port 993 SSL/TLS
SMTP mail.example.com port 587 STARTTLS
Username [email protected]
Password the password you just setHestiaCP runs Exim and Dovecot for mail, and installs Roundcube as webmail on many setups, usually at https://example.com/webmail. To test delivery on the server:
tail -f /var/log/exim4/mainlogFor reliable delivery you also need correct mail DNS:
Arecord formail.example.compointing at your server IPMXforexample.compointing atmail.example.com, priority 10TXTSPF, for examplev=spf1 a mx ip4:203.0.113.10 ~allTXTDKIM with the public key from the mail domainTXTDMARC at_dmarc.example.com, for examplev=DMARC1; p=none; rua=mailto:[email protected]- A matching reverse DNS (PTR) record for your server IP — see set your server hostname and reverse DNS
Point the domain at your server
Two routes, pick one:
Use HestiaCP as your DNS server. At the registrar, set the nameservers to the ones you run, for example ns1.example.com and ns2.example.com, with glue records for those hostnames pointing at your server IP. Every record is then managed in the panel.
Keep the registrar's DNS. Copy the A, MX, SPF, DKIM and DMARC values into the registrar's DNS editor. HestiaCP's local zone stays unused.
Nameserver changes and record edits can take a while to propagate, and mail sent to the old destination during that window may be lost. Do the change when you can watch the results, and keep the old mail host running until the new one receives test mail.
Check what the world sees:
dig +short example.com A
dig +short example.com MX
dig +short example.com TXT
dig +short example.com NS @1.1.1.1Check it works
- Load
http://example.comin a browser. You should get your uploaded file or the panel's default page, not the HestiaCP login. - Issue a certificate: in Web, edit the domain, open SSL Support, choose Let's Encrypt and save. Then confirm with
curl -I https://example.com. - Send a message from an outside account to
[email protected], then reply from Roundcube or your mail client. - On the server,
tail -f /var/log/exim4/mainlogshould show the message arriving and leaving without deferrals.
Troubleshooting
- The browser shows the panel or a default page for your domain → DNS is not pointing at this server yet, or the request is landing on another virtual host. Re-check
dig +short example.com Aand compare it with your server IP. - No DNS zone appeared after adding the domain → DNS support is off for that user's package. Turn it on in the panel, or add the zone by hand under DNS → Add Domain.
- Record edits seem to have no effect → you are probably querying a cached resolver. Test the authoritative side with
dig @203.0.113.10 example.comand allow the record TTL to expire. - Mail lands in spam or is rejected → missing or wrong PTR, SPF or DKIM. Fix reverse DNS first, then re-check the
TXTrecords withdig. - Mail sits in the queue and never sends → outbound port 25 may be blocked upstream. Check the Exim log for connection timeouts, and ask your provider whether port 25 is allowed.
Next steps
- Postfix and Dovecot mail server setup on a Linux VPS if you want to understand what sits under HestiaCP's mail stack.
- Set your server hostname and reverse DNS before you send mail from a new IP.
- Add a swap file on a Linux VPS if your panel and mail services are tight on memory.
- Compare plans on the Linux VPS hosting page when you are ready to host more sites.
Was this guide helpful?
Still stuck?
Ask RunRacks AI for a quick answer, or open a ticket and our team will take a look at your server.
Related guides
Control panels
How to install Plesk on a Linux VPS (AlmaLinux and Ubuntu)
Install Plesk on a fresh Linux VPS with the official one-click installer, apply your licence key and log in to the panel for the first time on port 8443.
- Beginner
- Linux VPS
- 8 min read
Control panels
CyberPanel: back up and restore a website
Create on-demand and scheduled website backups in CyberPanel, download the archives off the server, and restore a site from a backup when something breaks.
- Intermediate
- Linux VPS
- 6 min read
Control panels
Plesk Backup Manager: schedule backups and restore a site
Set up scheduled backups in Plesk Backup Manager, keep a copy off the server, and restore a single domain or subscription when something goes wrong.
- Intermediate
- Linux VPS
- 7 min read