Adding a Domain in Plesk: Subscriptions, DNS, the Certificate, and What Breaks in Between

To add a domain in Plesk, open Websites and Domains, click Add Domain, enter the name, choose whether it hosts a website or forwards elsewhere, and confirm. Plesk creates the document root, a DNS zone and, if the domain already resolves to the server, can issue a free certificate in the same flow. Most of the trouble comes from the parts around that click path: which subscription the domain lands in, whether the DNS zone Plesk created is actually in use, and the order in which DNS and the certificate have to happen.

The documentation gives you the click path in two lines. The support threads are full of people who followed it and got a default page, a certificate error, or a domain that mysteriously belongs to a different customer. This post is the two lines plus the model that makes the errors make sense.

Table of contents

• Domains, subscriptions and the thing Plesk calls a webspace
• Adding the domain, step by step
• DNS: is Plesk the zone, or is the registrar?
• The certificate
• What breaks, and the fix for each
• What this looks like without a control panel
• How this fits the rest of the stack
• FAQ

Domains, subscriptions and the thing Plesk calls a webspace

In Plesk a domain does not stand alone. It lives inside a subscription, which is the unit that carries the hosting plan, the resource limits, the system user and the home directory. The first domain in a subscription is the one it was created with; every further domain added to it shares the same system user and limits, and gets its own document root under the same home.

That distinction decides the first choice you make. Adding a domain to an existing subscription is right when the new site belongs to the same customer or the same project. Creating a new subscription is right when it is a different customer, needs different limits, or should be isolated so that one site’s problems do not become another’s. On a server you administer, this is the difference between Websites and Domains, which adds to the subscription you are in, and Subscriptions, which creates a new one.

Plesk also has two lighter shapes. A subdomain is a name under an existing domain with its own document root. A domain alias is a second name that serves exactly the same site as an existing domain, which is what you want for the .net and .org of a .com, not a separate domain.

Adding the domain, step by step

1. Log in, open Websites and Domains, and confirm you are in the right subscription. If you administer several, the subscription selector at the top is where domains end up in the wrong place.
2. Click Add Domain. Recent versions ask what you want to create: a blank website, a website from a Git repository, a WordPress site, or a forwarding domain. Pick blank for anything you will upload yourself.
3. Enter the registered domain name, without www. Plesk adds www as an alias by default.
4. Hosting type. Website hosting creates a document root and serves files. Forwarding sends visitors to another URL with a 301 or a frame. No hosting registers the domain for DNS or mail only.
5. Document root. The default is a folder named after the domain under the subscription’s home. Change it only if you have a reason.
6. IP address, if the server has more than one. Leave the default unless you know why it should differ.
7. Confirm. Plesk creates the folder, the virtual host configuration and a DNS zone, and shows the domain with a default page.

At this point the domain exists on the server and nowhere else. Whether visitors reach it depends entirely on the next section.

DNS: is Plesk the zone, or is the registrar?

Plesk creates a DNS zone for every domain it hosts, with A records pointing at the server, MX records for its own mail, and the usual set. That zone is only consulted if the domain’s nameservers, set at the registrar, point at this Plesk server. In most small setups they do not: the nameservers stay with the registrar or a DNS provider, and the zone Plesk built is decorative.

So the check is: where are the nameservers? Run dig NS example.com or look at the registrar’s control panel. If the answer is not this server, the records that matter are the ones at the registrar, and you need an A record for the apex and one for www, both pointing at the server’s public IP. Edit those there, not in Plesk.

dig NS example.com +short          # who is authoritative
dig A example.com +short           # what the apex resolves to right now
dig A www.example.com +short

If you do want Plesk to be authoritative, because you are running many sites and want the zones in one place, set the nameservers at the registrar to the Plesk server’s hostnames and register glue records for them. Then the DNS Settings tab on each domain is the real thing, and changing an A record there changes where the site resolves.

The certificate

Plesk ships an extension that issues free certificates through an automated authority and renews them. It works well, and it has one hard requirement: the domain must already resolve to this server on the public internet, because the authority proves control by fetching a file from it. Order the certificate before the DNS has propagated and it fails with a message about a challenge that could not be validated. Wait, check with dig from outside the server, then try again.

Under the domain, open SSL/TLS Certificates, choose the free option, tick the domain and its www alias, and confirm. If the extension is not installed, it is in the extension catalogue and takes a minute. Once issued, turn on the permanent redirect from HTTP to HTTPS on the Hosting Settings page and enable HSTS only after you have confirmed the certificate renews correctly, because an HSTS header with a lapsed certificate locks visitors out.

A wildcard certificate, covering every subdomain, requires a DNS challenge instead, and that only works when Plesk controls the zone or is connected to the DNS provider’s API. If the nameservers are at the registrar and the registrar is not integrated, issue per-subdomain certificates instead.

What breaks, and the fix for each

• The domain shows a default Plesk page or a different site. The document root is empty, or the request matched a different virtual host because DNS points at a server that does not have this domain. Upload something to the document root; confirm the A record.
• The domain already exists on this server. It was added to another subscription, sometimes by a previous customer. Find it under Subscriptions, remove or move it, then add it again where it belongs.
• The certificate fails to issue. DNS has not propagated, the A record points elsewhere, or port 80 is blocked by a firewall rule in front of the server. Check all three from outside the server before retrying.
• The site works on www but not the apex, or the reverse. One of the two A records is missing, or the alias was removed. Both names need to resolve, and the redirect to the canonical one belongs in Hosting Settings.
• PHP errors after adding the domain. Each domain has its own PHP version and handler in Plesk. Match the new domain’s setting to the one the application needs.
• Mail stops working after moving DNS to Plesk. The MX records in the Plesk zone point at the server, and the mail was elsewhere. Copy the old MX records into the new zone before switching nameservers.

What this looks like without a control panel

Every step above exists because a control panel manages a server, and a server has a filesystem, a virtual host configuration, a DNS daemon and a certificate client that all have to agree. That is the right tool when you need the server. It is a lot of surface area when what you needed was a domain pointed at a site.

On a managed platform the same task is shorter. On RunxBuild, adding a domain to a static site or a service is the domain name and one DNS record at your registrar; the certificate is issued and renewed without a request, and the www and apex handling is a setting. The custom domains docs cover the record to set. For the WordPress case the panel’s job, files and database, is a file manager and a database browser in the dashboard, from the $3 Starter plan. The subscription model, the zone that may or may not be in use, and the challenge that fails before DNS propagates are not things you configure, because there is no server underneath for them to belong to.

How this fits the rest of the stack

A control panel is worth its administration when the server is the product. When the site is the product, the RunxBuild hosting calculator shows what the site actually costs to run as line items, the static hosting or the service plan, the database, the storage and the bandwidth, without a server to manage in the middle.

Useful related references:

• The .pt Domain: Who Can Register One, and What to Do Next
• What Is a .link Domain, and When Does It Fit a Project?
• .ES Domain: Requirements, the ID Rules, and Setting It Up
• Custom domains and certificates on RunxBuild

FAQ

How do I add a domain in Plesk?

Open Websites and Domains, click Add Domain, enter the name without www, choose website hosting, accept the default document root and confirm. Plesk creates the folder, the virtual host and a DNS zone. Then make sure the domain’s A records, wherever its nameservers actually live, point at the server.

What is the difference between a domain and a subscription in Plesk?

A subscription is the container: hosting plan, resource limits, system user and home directory. A domain lives inside one. Add a domain to an existing subscription when it belongs to the same customer or project; create a new subscription when it needs separate limits or isolation.

Why does my new Plesk domain show the default page?

Either the document root has nothing in it yet, or DNS is pointing at a different server that does not know the domain. Upload the site to the document root and check with dig that the A record resolves to this server’s public IP.

Why does the free SSL certificate fail in Plesk?

The domain must already resolve to the server over the public internet, because the certificate authority validates by fetching a file over HTTP. Wait for DNS to propagate, confirm with dig from outside the server, check that port 80 is reachable, then order the certificate again.

Do I need to change nameservers to use Plesk DNS?

Only if you want Plesk to be authoritative. If the nameservers stay at your registrar, the zone Plesk creates is not consulted and you manage A, CNAME and MX records at the registrar instead. Pointing nameservers at Plesk makes the DNS Settings tab the live zone.