wolstech Posted May 4 Posted May 4 Placing a domain inside another domain is not a normal or supported configuration. While technically possible to do, placing the document root of a domain inside of another domain's root can break things (e.g conflicting .htaccess files, some features like node will not work right especially when accessed through the parent domain, etc.), requires manual configuration on our part since our system is designed to create them side by side automatically, and users don't like the fact that the content of the nested domains are accessible from the parent domain (SEO and security issues). Ironically, our old cPanel based system actually required this and people hated it...eliminating the requirement that all addon domains be inside the main domain was actually one of the major improvements provided by our switch to Plesk. People who migrated from cPanel actually still have domains running like this, and those accounts are often so broken (for a combination of reasons, not just nested domains) that we recommend resetting them... You're one of only two I'm aware of to actually ask for this. Is there a reason you really want to do this?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now