check the alias name in website setting. you will find it that way.

The problem is you need your DNS settings wildcard setup so that you can simply type in the full url - eg.. http://child.thatdomain.com (parent) rather than http://www.thatdomain.com/child (child) otherwise you can't access the portal.

It means that if you don't have the wildcard setup - the * setting that allows you to put in anything.thatdomain.com and it will default to the home page if it's non existent - eg.. try http://nina.dotnetnuke.com or your name or whatever, they have wildcard setup here..   You will have to set up first in DNS under the A record - just add another entry with the name of the portal subdomain.. eg.. in this case - the A record would be child.   It doesn't even require an IIS setup which makes it so handy to work with and clean in folder structure.

Child portals always produce a folder with it's own default.aspx file in it, and it can get very cluttered if you have alot of them.  Also when deleting the portal, I don't think it deletes that folder, and then you have that alias at the end which I simply don't like, even in a demo/test environment for my clients.

The trick is to get your DNS setup correctly and then you can use this repeatedly when building your children portals (whether they end up as parent/full domains or not) and keep the folder structure clean.

Nina Meiers