Hello,
I posted some info on working with portals here:
http://www.dnncreative.com/Forum/ta...fault.aspxHave a play with these settings in a localhost installation and you will see how it works.
Basically you can create a Parent portal ie: www.mywebsite.com or a child portal ie. www.Northern-KY.com/firstportal
You can do this direct in your current DNN installation without doing any additional installations.
If you are doing this within a live website you will need to set in your hosting the domain name to point to your DNN installation - so this will be just the same as setting it up when you first point your domain name to your DNN installation.
One thing to think about is generally when you buy hosting, they provide a domain for each SQL server so you may find that when you ask for an additional domain name to point to your installation it costs pretty much the same as another separate hosting package.
Something else to think about is backup / uptime - If you install all of your sites into one DotNetNuke installation, make sure you can back everything up. - What happens if something becomes corrupted? All of your sites will be brought down.
I personally create separate DNN installations to make it easy to backup separate sites and to ensure that if anything goes wrong, all of my other sites will carry on working ok - Just something to think about, I know of people who have installed large numbers of portals to just one DotNetNuke installation.
Thanks,