Quote Originally Posted by lhungil View Post
This sounds like an issue with the way your hosting company (or you via cPanel) configured the new domain. You need to define separate public_html folders for each domain (cPanel calls them "document root"). This eliminates the need for complicated .htaccess rules in each folder to handle redirections caused by two domains sharing a document root.

If your hosting provider has your site structured with "/username/public_html"... You can configure separate document root folders using cPanel for the second domain. This MUST be done when the domain is added. If it was not you would need to remove and re-add the domain. Under cPanel go to "Domains" > "Add-On domains". You should see the option to remove existing domains and also the option to add a new domain. One of the fields when adding a domain is "document root". This would then become "/username/domain2/public_html". Why the extra folder in the middle? So your new domain has somewhere to place sensitive files such as "cache", "logs", and other data if needed.

If your hosting provider does not give you write access to a folder below the "public_html" (document root) folder, you may want to look at a different provider. Having a place to store sensitive data is a good idea, and lets you setup multiple domains with less hassle.

I have a few clients who have multiple domains hosted with companies using cPanel and this method works well.

Alternatively you can add an exclusion to the .htaccess rules added by CEON URI Mapping to exclude requests made for domain2.com. But you will have to make a number of changes in domain2.com for domain2.com's .htaccess rules to work with CEON URI Mapping... It will be easier and better in the long run to just configure both domains on the server (via cPanel) with separate "public_html" (document root) folders.
Can this also be done with an ftp client?