So I have my domain name mapped to the ip address of the shared hosting server I am using on Godaddy....I believe the first step is done.

I see about putting that domain name as the http alias but tell me a little more about domain in relation to dotnetnuke please. Should it be at root?

Also, now that I mapped the domain to the server, I get an invalid hostname. Does dotnetnuke at like a form of a dns server withing my hosting account?

Mitchel,

I see what your doing by setting up the different portals and I have been able to setup a child portal without a problem except that I cannot get an http alias to point to the folder...I must be doing something wrong. Here's more info:

When I make a child portal of the main dotnetnuke portal I add an additional level and the child portal works fine making the additional folder and the default.aspx file is made. If I add an additional alias (http://www.mydomain.com), should I forward the domain to the folder containing the default.aspx.....such as http://www.mycompany.com/dotnetnuke/newfolder/.......this is where I have a problem.

And number two, If I make a parent portal I have ome problems. Here's what happens.
I map the dns to the server's ip address as suggested in the dotnetnuke online documentation. The domain becomes unknown when browsing to it. I then make a parent portal with an http://www.samedomain.com and dotnetnuke does not make a folder and there is no default.aspx for the domain to go to.


Should I just be making child portal to introduce new websites:

Thanks for your help

Larry Repasky
nashville, TN