A subdomain in ISPmanager 6 is created as an ordinary site with a name like name.example.com, its own folder on disk, and its own certificate. It does not inherit the main site's settings automatically — it is a separate entry in the panel.
How a subdomain differs from a domain and from a site folder
These three concepts get mixed up the most, even though they solve different tasks and look different to a visitor in the address bar.
| Trait | Domain | Subdomain | Site folder |
|---|---|---|---|
| Look in the address bar | example.com | name.example.com | example.com/name |
| Own DNS record | yes, required | yes, separate | not required |
| Own certificate | yes | yes, separate or via wildcard | shared with the site |
| Separate panel section | yes | yes, as a separate site | no, part of the site |
Creating a subdomain step by step
A subdomain in ISPmanager 6 is set up through the same section as an ordinary site, with the full subdomain name entered instead of the domain name.
- open the "Domains" or "WWW domains" section in the panel
- add a new domain and enter the full subdomain name, for example name.example.com
- point to the folder on disk where the subdomain's files will be uploaded
- choose the site owner from the panel's list of users
- choose a PHP version if the subdomain needs one different from the main site
- save and wait for the web server settings to take effect
DNS: when the record appears on its own, and when it does not
If the domain's zone is served on this same server and managed through ISPmanager, the panel adds the subdomain's record automatically when the site is created. If the domain is served by a different DNS server or an outside registrar, the A or CNAME record for the subdomain needs to be added by hand in the zone where the domain lives. More on manual setup is in the article on subdomains: creating and configuring.
Certificate for a subdomain: separate issue or wildcard
For a single subdomain it is simpler to issue a separate certificate for its name, and the panel does this the same way as for the main site. If there are many subdomains and they appear often, a wildcard certificate for *.example.com is more convenient — it covers any first-level subdomain without a separate issue for each one.
Separate PHP version and separate limits for a subdomain
A subdomain, being a separate site, gets its own PHP settings and its own resource limits, independent of the main site. This is handy for a test copy of the site on a new PHP version or for a section under heavier load that should not eat into the main domain's limits.
Common mistakes when creating a subdomain
| Symptom | Cause | What to check |
|---|---|---|
| Subdomain opens the main site | subdomain folder is pointed wrong | folder path in the site settings |
| "Site does not exist" | no DNS record, or the old TTL has not expired | dig output for the subdomain name |
| Certificate is not issued | DNS record is not yet visible from outside | whether the name resolves from the internet |
| Owners are mixed up | subdomain was created under a different panel user | owner field in the site settings |
Removing a subdomain without losing data
Removing a subdomain site in the panel drops the web server entry and the PHP settings, but the files in its folder can be left untouched if directory cleanup is not selected during removal. The panel does not remove the DNS record automatically if the zone is not run on this server, and it needs to be removed separately by whoever manages the zone. On creating a new site in the freed spot, see the article on creating a site in ISPmanager 6.