This is not an issue, this is by design. The httpd-vhosts.conf file is controlled by Sentora.
You need to enter the domains in the Domain Manager module. And, if using Sentora's DNS you need to create each domain's DNS entries using the DNS Manager module.
I am not sure why anybody would use the system in the manner you are suggesting
But, to solve your question:
You could use the virtual host override feature to do what you are trying.
Module Admin > Apache Config > Override a virtual host > [select domain] > Custom Entry:
Or:
Module Admin > Apache Config > Global Sentora Entry:
Pay attention to how the above is written! </virtualhost> closes the previous vhost entry and Sentora will add the closing </virtualhost> at the end automatically.
Check 'Force Update' and Save. Wait ~5 minutes for changes to take affect.
You need to enter the domains in the Domain Manager module. And, if using Sentora's DNS you need to create each domain's DNS entries using the DNS Manager module.
I am not sure why anybody would use the system in the manner you are suggesting
But, to solve your question:
You could use the virtual host override feature to do what you are trying.
Module Admin > Apache Config > Override a virtual host > [select domain] > Custom Entry:
Or:
Module Admin > Apache Config > Global Sentora Entry:
Code:
</virtualhost>
<virtualhost *:80>
ServerName mydomain.com
ServerAlias *Pay attention to how the above is written! </virtualhost> closes the previous vhost entry and Sentora will add the closing </virtualhost> at the end automatically.
Check 'Force Update' and Save. Wait ~5 minutes for changes to take affect.
