Recently, a customer ran into an issue in DirectAdmin where they were able to access their subdomain directory as a sub-directory of their main domain. This might not be a major issue for everyone, but it is still a concern that should probably be addressed.
By default, when you add a subdomain through the Subdomain Management page, it creates the subdomain directory in the following tree:
When you think about how that would work, you realize that you are able to access the subdomain via {domain}/{subdomain}. This may cause some issues with the configuration of their site and possibly even cause issues with their SEO rankings.
You may be tempted to recreate the subdomain entry and change either the private_html or the public_html directories. However, you’ll come to find that DirectAdmin does not handle this well and still does not utilize the new directory. Instead, DirectAdmin sticks to utilizing the folder under the main domain as the public_html directory.
The best way around that we were able to find is to add the subdomain in the Domain Setup page.
While that was not a difficult fix, this is something we are looking forward to having DirectAdmin fix going forward.
Have you run into any other issues like this? Do you need assistance with your site? Feel free to either submit a ticket or email us for assistance!