- Plesk for Linux
- Plesk for Windows
Note: The article is applicable if example.com's DNS zone is managed by Plesk. If no, add the appropriate A record using the instructions.
There is no A record for the subdomain in the primary domain DNS zone at Plesk > Domains > example.com > DNS settings;
Subdomain sub.example.com can not be resolved.
# nslookup sub.example.com
** server can't find sub.example.com: NXDOMAIN
Primary domain example.com is resolved to Plesk server properly:
# dig +short example.com
DNS zone for the primary domain is hosted in Plesk:
# dig ns +short example.com
# dig +short ns1.example.com ns2.example.com
DNS service is disabled for the subdomain in Plesk > Domains > subdomain.example.com > DNS settings;
Missing A record for the subdomain.
DNS service is not enabled for a subdomain by default. Plesk creates A record for a subdomain in the primary domain DNS zone.
Add A record to the primary domain DNS zone:
- Login into Plesk.
- Navigate to Home > Domains > example.com > DNS Settings > Add record:
Enable DNS service for subdomain in Plesk:
Navigate to Home > Domains > subdomain.example.com > DNS Settings.
In case the primary domain's DNS zone is hosted on registrar's side (not on the Plesk server), add the appropriate A record using instructions from the following article:
How to configure name server for domain on registrar's side
Note: It is known that some time is needed to propagate DNS changes (it can take up to 48 hours).