Plesk DNS settings for Wildcard Subdomain + SSL Support
The Plesk Integration enables automated DNS management for your SaaS tenants using wildcard subdomains (e.g., *.yourcrm.com
). This setup simplifies tenant provisioning by eliminating the need to manually configure DNS records for every new tenant.
β
Prerequisites
Ensure the following before proceeding:
Your domain (e.g.,
yourcrm.com
) is added and hosted on Plesk.You have root access to your Plesk server.
A wildcard SSL certificate (Let's Encrypt or custom) is installed or ready to install.
π Step 1: Add Wildcard DNS Record
Option 1: DNS Managed by Plesk
Log in to Plesk.
Navigate to:
Websites & Domains β yourcrm.com β DNS Settings
.Click Add Record and enter:
Record type: A
Domain name:
*.yourcrm.com
IP address:
<Your Server IP>
Click OK, then click Update to apply the changes.
Option 2: External DNS Provider (e.g., Cloudflare)
Log in to your DNS provider dashboard.
Add the following A record:
Type: A
Name:
*
or*.yourcrm.com
(depending on the provider)Value:
<Your Server IP>
TTL: Auto or 300
π Step 2: Configure Wildcard Hosting in Plesk
Plesk does not expose wildcard subdomain creation via its GUI, but it can be configured via SSH.
Option A: Default Apache/Nginx Hosting
Connect via SSH to your Plesk server as root.
Run the following to create a wildcard subdomain:
Check your web server configs:
For NGINX:
/etc/nginx/plesk.conf.d/vhosts/
For Apache:
/var/www/vhosts/system/yourcrm.com/conf/httpd.conf
Ensure these lines exist:
NGINX:
server_name *.yourcrm.com;
Apache:
ServerAlias *.yourcrm.com
π If not present, manually add and restart services:
β οΈ Manual edits may be overridden by Plesk updates. Use Plesk custom templates for persistent changes.
π Step 3: Install Wildcard SSL Certificate
Wildcard certificates require DNS-01 verification.
In Plesk:
Websites & Domains β yourcrm.com β SSL/TLS Certificates β Let's Encrypt
.Enable:
β Secure wildcard domain (via DNS-01 challenge).
Add the required TXT record in your DNS provider (if not handled automatically).
Complete the verification and install the certificate.
β
Youβre Done!
Your wildcard subdomain setup on Plesk is now ready for concord SaaS use. Every new client (e.g., client1.yourcrm.com
, client2.yourcrm.com
) can access their own instance with zero manual DNS or vhost configuration β it's all dynamic and scalable.
Last updated