Quick question....

I am working on a new site for a customer and they don't have a domain name yet so I creatd a child portal for demonstration purposes.  When the client gets a domain name and I point it to my DNN site, when I change the alias from http://www.123.com/abc to www.abc.com, is the site now a parent portal?

Is so, can I then remove the folder DNN created because it was a child portal or do I have to leave the folder there?

Thanks,

Jason

Thanks for the information.  I will keep this in-mind when creating the site.

I recently completed this successfully.  The following steps worked for me:

• Dnn is installed in the directory www.domain1.com.
• A child portal exists (www.domain1.com/child). We want a new domain name (www.domain2.com) to become the url for his portal (i.e. it would be a parent portal, no longer a child of the main installation at www.domain2.com).
• So, logged in as Host, go to the Site Settings of the child portal and add a new portal alias for the new domain name. (Admin: Site Settings: Advanced Settings: Site Aliases)
• At the registrar for www.domain2.com, point the new domain name to the name servers of the hosting provider.
• At the hosting providers, point www.domain2.com to www.domain1.com (i.e. where the dnn is installed - or with some hosts such as GoDaddy, this means using a hosting control panel to add the www.domain2.com alias)
• YOu may need to wait 48 hours for these changes to propagate (also clear your browser cache).
• Browse to www.domain2.com. At this point the dnn installing should be working at this new directory. 
• While in the main portal but under the new domain name, go to Site Settings > Portal Aliases and make www.domain2.com the "Default Alias.
• Then you may  delete the child portal alias.
• You are done