I am getting some odd behaviour when trying to configure a child portal with another alias.  I have created a domain pointer pointing to the child portal folder in the DotNetNuke file system.  However, when I double click on the new alias (e.g. www.myalias.com) it redirects me to the default dotnetnuke install page which is configured in a virtual directory format: http://www.mydomain.com/dotnetnuke/test/. Whereas when I double click the default portal alias (for the child portal)  I am redirected to http://www.mydomain.com/DotNetNuke/test/Default.aspx?alias=mydomain.com/dotnetnuke/test/child which is the child portal welcome page.  I believe the reason for the discrepency is how the default.aspx file found in the child portal folder handles incoming URLs.  Is there something I'm missing or perhaps the domain pointer is setup incorrectly?  Currently my web hoster sets a hostheader in IIS and points the hostheader to the appropriate folder in the filesystem.  Thanks in advance.