How to Add a Domain and Subdomain in Plesk Obsidian

Plesk lets you host several websites from one control panel. A domain can have its own website, PHP settings, database, mail, SSL certificate, logs, and system user. A subdomain, such as shop.example.com, can use a separate document root while staying under the main domain.

This guide shows how to add a domain and subdomain in Plesk Obsidian, connect DNS, upload a site, enable HTTPS, and check the setup without mixing unrelated database and mail tasks into the process.

Before Adding a Domain to Plesk

• Register the domain with a domain registrar.
• Confirm that your Plesk plan allows another domain or subdomain.
• Know whether DNS will be managed by Plesk, your registrar, or another provider.
• Take a backup before moving an existing live website.
• Lower the DNS TTL in advance if you are planning a migration.
• Keep the old hosting active until the new website and email are tested.

Adding a domain inside Plesk does not register the name and does not automatically change records at an external DNS provider.

Domain, Subdomain, and Domain Alias

Option	Example	Use it when
Domain	example.com	You want a separate website and hosting settings
Subdomain	shop.example.com	You want a section or separate app below an existing domain
Domain alias	example.net → example.com	Another registered name should show or redirect to the main site

Do not add an alias as a separate duplicate website. Duplicate sites can split traffic and create SEO problems. Choose one preferred URL and redirect aliases to it.

Add a New Domain in Plesk

1. Sign in to Plesk over its HTTPS address.
2. Open Websites & Domains.
3. Click Add Domain.
4. Choose a blank website, file upload, WordPress, Git deployment, Sitejet, or mail-only hosting as needed.
5. Select Registered domain name and enter the domain without http:// or a path.
6. Choose an existing webspace/subscription, or create a new one if your permissions and hosting plan allow it.
7. Review the system user, document root, IP address, and hosting type.
8. Click Add Domain.

The exact choices depend on the Plesk edition, view mode, extensions, and permissions set by the hosting provider. If the button or a field is missing, check the subscription limit or ask the administrator.

Choose the Correct Hosting Type

• Website hosting: Plesk stores and serves the site’s files.
• Forwarding: visitors are redirected or framed to another URL.
• No web hosting: useful when the domain only needs DNS or mail.

For a normal website, select website hosting. Keep each unrelated website in its own document root. Sharing one folder between domains can cause accidental data exposure and makes future moves difficult.

Connect the Domain’s DNS

You have two common choices. With Plesk as the authoritative DNS server, change the domain’s nameservers at the registrar to the names shown under Websites & Domains → Hosting & DNS → DNS. Make sure the nameserver hostnames have the required address or glue records.

With external DNS, keep the current nameservers and create records at that provider. A simple web setup normally needs:

• An A record for the root domain pointing to the Plesk IPv4 address
• An AAAA record only if IPv6 is configured and reachable
• A www CNAME to the root domain, or the matching A/AAAA records
• Separate MX, SPF, DKIM, and DMARC records when mail is hosted elsewhere or in Plesk

Do not copy Plesk’s mail records if another provider handles email. Changing nameservers without copying the complete old DNS zone can stop mail and other services.

Verify DNS Before Installing SSL

dig +short A example.com
dig +short A www.example.com
dig +short AAAA example.com
dig +short MX example.com

Run checks from more than one network if possible. DNS changes can take time according to previous TTL values. A wrong AAAA record may send some visitors to another server even when IPv4 is correct.

Upload or Deploy the Website

Open the domain in Websites & Domains and use one supported method:

• File Manager: upload and extract a small site into the document root, usually httpdocs.
• SFTP: safer than plain FTP for regular file transfer.
• Git: deploy from a controlled repository if the Git extension is available.
• WP Toolkit: install or manage WordPress with Plesk’s WordPress tools.
• Migration tools: move a live site with files, database, and settings using a tested process.

Do not leave backup archives, database dumps, or configuration secrets inside a publicly reachable document root. Check file ownership and permissions instead of using 777.

Enable HTTPS in Plesk

1. Wait until every requested hostname resolves to the Plesk server.
2. Open the domain’s SSL/TLS Certificates or Let’s Encrypt action.
3. Enter a monitored email address.
4. Select the root domain and www only when both DNS records are correct.
5. Request the certificate.
6. Open Hosting Settings and enable the permanent HTTP-to-HTTPS redirect if suitable.
7. Test both the HTTP and HTTPS URLs.

Certificate names must match the public site. If issuance fails, check DNS, IPv6, port 80, proxy/CDN settings, and the Plesk Let’s Encrypt log before repeating requests.

Add a Subdomain in Plesk

1. Go to Websites & Domains.
2. Click Add Subdomain.
3. Enter only the label, such as shop.
4. Select the parent domain.
5. Choose a separate document root such as shop.example.com or the value Plesk suggests.
6. Click OK.
7. Check or create the subdomain DNS record.
8. Upload the application and issue a certificate for the subdomain.

A wildcard subdomain uses * and catches undefined subdomain names. Use it only when the application is designed for that behavior. It does not automatically create a wildcard TLS certificate.

Set PHP and Application Options

Under the domain, open PHP Settings and choose a PHP version supported by the application and Plesk server. Avoid unsupported PHP versions. Change memory, upload size, or execution settings only when the application needs them and the hosting plan permits it.

Create a separate database and least-privilege database user for the site. Keep database credentials outside public files where the framework supports environment configuration. Our database user guide explains the least-privilege idea.

Test the New Website

• Root domain and www reach the intended site.
• HTTP redirects to the chosen HTTPS URL once.
• The certificate covers each hostname and is trusted.
• Forms, login, uploads, database, scheduled tasks, and outbound email work.
• No private archive or default Plesk page is exposed.
• Backups include the new files, database, and mail where required.
• Monitoring checks the final HTTPS URL.

Removing a Domain Safely

Removing a domain in Plesk can delete its website data and related services from the server. It does not cancel domain registration. Export files, databases, DNS, certificates, mail, and logs first, verify the backup, and confirm that no other domain shares the document root. Then use Remove Website or Remove Subdomain.

Frequently Asked Questions

Why is Add Domain missing?

The subscription may have reached its domain limit, or the account may not have permission. Check the hosting plan or contact the Plesk administrator.

Why does the Plesk default page appear?

DNS may point to the wrong IP, the domain may be assigned to another subscription, or the document root may still contain the placeholder. Check DNS and Hosting Settings.

Does adding a domain create email automatically?

No. Mail availability depends on the subscription and server. Create mailboxes separately, or preserve the external provider’s MX and authentication records.

Conclusion

You have added a domain or subdomain to Plesk, connected DNS, deployed files, enabled HTTPS, and tested the site. The most important migration rule is to keep DNS, web, database, and mail changes coordinated so one service does not break while another moves.

Before making larger changes, review our Plesk remote backup guide.

---

Reviewed and updated: August 2026. Steps were checked against Plesk Obsidian’s official documentation for adding domains, adding subdomains, and putting a website online.