Subdomains on Separate Packages #

Yes, you can create a subdomain as a primary hosting package on StackCP. This allows you to host the subdomain separately from the main domain name, even on a different platform such as Linux, WordPress, Managed VPS, or other supported platforms.

Note: Disabling any of the subdomain packages will result in all packages being disabled because disabling is done on a per-domain basis, rather than on a per-package basis. For example, you can have example.com as a WordPress package and sub.example.com as a Linux package.

Important: Before you can create the subdomain hosting package, you must have a hosting package for the primary domain. DNS for both the main domain and subdomain is controlled from the main domain name’s Manage DNS section in the main domain name’s package. The Manage DNS section will not show on the subdomain package.

Examples:

• example.com
• sub.example.com

Conflicts #

• You won’t be able to create a subdomain if it already exists elsewhere in your account. If you want to add the subdomain as a package, it first needs removing from the main domain’s package if it already exists there.
• If the subdomain exists as its own package, you won’t be able to add it as a subdomain to the main domain’s package.
• If you see the warning “You need to have DNS authority for example.com before you can add sub.example.com,” it means another customer has a hosting package for example.com with authority. At StackCP, we allow you to create a hosting package using a ‘domain reference’, i.e., a domain that’s not linked to any live DNS. In cases where two packages exist with the same name, we must give ‘authority’ to one of them. This warning indicates that another customer has authority over the domain name.