Addon Domain Directories Visable

[TekDog]

When I started BH with my pilot account the directory structure was rooted on public_html. When I started to add Addon Domains I rooted them to subdirectories below public_html. What i discovered was that i could access every one of the addon's by specifying the mydomain.com/addondomain. Ouch!

So I modified the .htaccess file (as per http://helpdesk.bluehost.com/kb/inde...od_id=2&id=394) to point the pilot domain to its own folder below public_html alongside the addon domains. This is working fine now for the pilot account but I can still specify the addon directory in the URL and get to it!

How can I get around this? It acts like a redirect to the content in the root subfolder but then also acts as a reference to the public_html as the relative root?

Shouldn't i be able to host the pilot and addon domains in separate folders under public_html and maintain independence? Or, do i have to point my root account to a bogus domain and just use the addon's?

Anyone have any thoughts?

[felgall]

They are independent because no one will know that those folders exist since no link to the actual folder exists anywhere - particularly if your add-on domain example1.com is in a folder called example.com/easdfbgk