Addon domains are a special type of subdomain. They are read from the Apache configuration file. There are a number of reasons that what you describe could happen, and we would need to see your server in order to determine why this happened and correct it. Please submit a ticket so that we may investigate this directly and correct it for you.

Any idea about what caused this issue. I have had the same issue as well but not only did I loose the Addon domains but the email accounts are gone as well.

Click to expand...

Tymsah, please let me know the support request ID number from your ticket submission. For the benefit of others I would like to try to help determine the specific cause and relay detail of the resolution.

Staff Member

Tymsah, please let me know the support request ID number from your ticket submission. For the benefit of others I would like to try to help determine the specific cause and relay detail of the resolution.

Click to expand...

I believe I was able to locate the specific ticket based off of the description provided here in the forums.

The notes provided indicate the issue may have stemmed from the the add-on domains not yet being successfully added into the Apache/httpd configuration (i.e., the necessary entries for the add-on domains were not yet added to the Apache/httpd configuration). The add-on domains did not yet exist in the Apache/httpd configuration because a syntax error prevented the configuration from being successfully updated (i.e., regenerated to include new information or applicable modifications) at the time the add-on domains were added. The syntax error was triggered from a custom entry in an include file of a specific Apache virtualhost. The resolution was to disable the custom entry that caused the syntax error and then regenerate or rebuild the Apache/httpd configuration.

The Apache/httpd configuration may be regenerated using the following utility via root SSH access:

Code:

/usr/local/cpanel/bin/build_apache_conf

A basic syntax check can be performed using the following:

Code:

# /usr/local/apache/bin/apachectl configtest

The aforementioned utility may also be accessed via two symbolic links (symlinks) as noted below (that might be easier to remember):

Code:

/scripts/buildhttpdconf
/scripts/rebuildhttpdconf

When the Apache/httpd configuration is updated, it is necessary to trigger a restart of the affected service; here are three commands that each accomplish the same goal of restarting Apache/httpd:

Tymsah, please let me know the support request ID number from your ticket submission. For the benefit of others I would like to try to help determine the specific cause and relay detail of the resolution.