Hi Dave -

the "bugger" I was referring to was that on my GoDaddy account, I originally wanted to set up just two DNN portals. So, I registered my hosting account with one of them. I found when I was in the GoDaddy Control Panel and went to the Domain Management screen, that I couldn't point that domain to a sub-directory because it was the main hosting account. I changed my hosting account to a third domain, and 24 hours later when that went through, I was able to re-add my intended domain and point it to the sub-directory where DNN was installed. You probably already know this, but the big advantage there is that I can type "www.domain1.com" to get to my site instead of having to have someone know to type "www.domain1.com/home" to get there. So - that's the first piece of the puzzle to getting my two parent portals working on GoDaddy.

The other piece was setting up the two portals with the proper aliases within the DNN Host menu's Portals page. Unfortunately, I had to define my portals with aliases "www.domain1.com/home" to get them to work, which meanas that even though I might type "www.domain1.com" to get there, I go to "www.domain1.com/home/Home/etc..." once I click on another tab. Very minor issue as far as I can tell. The only drawback I see is that the URLs are 5 characters longer than I'd like.

End result: I'm getting no redirect errors and you'd never be able to tell that those two domains are hosted on the same server (unless you did an nslookup or the like, obviously!) , let alone on the same database. This was a clean installation of DNN 4.4, by the way.

Hope that helps

Awesome - glad that helped. I don't understand why you need to do that, but whatever - as long as it works. I have aliases both with and without the subdirectory for each portal just to be safe.