I hate to post such a simple question but I can't find out how to do this exactly.  I have a hosting account where the dotnetnuke is alive.  I want to create a parent portal such that www.my-new-domain.com (as an example) is pointing to this new domain.

So what is required?  I have registered my new domain name and is on my shared hosting account.  How does www.my-new-domain.com know how to resolve?

I have read online articles that say things like, "you new domain name must point to your DNN instal..."  Does that mean point to where my dotnetnuke directory is or what?

I have bought a book on DNN 4.0 and there is nothing more than a paragraph about creating a parent portal in chapter 11. 

Any suggestions?

--Jeff

Here is exactly what I want to do.  I want to have a main portal (www.azlocals.com/dotnetnuke) where I have the ability to create independent website dynamically from (Parent Portals).  I have installed the DNN 4.5 in that location.

I created a Parent Portal called doorywebsolutions and registered a the domain name: www.doorywebsolutions.com. 

On my shared hosting, I point www.doorywebsolutions to www.azlocals.com/dotnetnuke.

The problem is that when I go to doorywebsolutions, I get forwarded to azlocals.com/dotnetnuke and DNN just treats me as if I went directly to azlocals.com/dotnetnuke.

What am I doing wrong?

--Jeff

Do you mean in the Portal Alias?  I have http://www.doorywebsolutions.com and it still just ends up at the DNN installation URL (http://www.azlocals.com/dotnetnuke).

What else could I be doing wrong?