Hi all,

OK I've set up my parent portals in this way..but I'm not sure if this is the 'correct' way or not!

1-created a new site in IIS alongside our standard intranet site and pointed it at the dotnetnuke installation directory.
2-started DNN to get the basic site
3-added a host alias of portal to the basic site
4-added a new parent portal with  host alias of testing
5-added two A(alias) entries into the intranets DNS (we only have one forward lookup zone) for portal and testing pointing at the webserver.
6-added the two host names portal and testing to the IIS site for DNN.

This works ok and I can now access two seperate portals by typing in either portal or testing in an intranet browser.

Any comments..?
Thanks
Rolf

Hey SlicerX,

What I meant is that within the IIS properties for your DNN site you can add hostnames;
Properties..Web site..IP..Advanced.

Here I have added all the aliases I have used in DNN for new Parent Portals..in my case Portal (for the first default installation) and Testing (for my first new parent portal).

Im not sure at what point DNN reads the host header name to decide which portal to push but having played with it I suspect it is AFTER IIS has looked so you still need the header host names in the IIS configuration.

So my set up is this;
DNN installed to c:\foo\bar
New site in IIS (or could use a virtual site) called DotNetNuke pointing to c:\foo\bar.
Initially the default site is given the local IP address as its alias, I changed this default alias to Portal.
Added Portal (on the local IP address) to the host header names
Added Parent Portal in DNN with the alias Testing
Added Testing (on the local IP address) to the host header names.

I had to add the two A records for Testing/Portal to the DNS server as well so all the intranet could find them using the 'friendly' names.

So basically if you type http://portal or http://testing the DNS points you at the web server..the web server reads the host header names and determines that these virtual sites reside in the DotNetNuke main site and then DNN determines which portals it should be pushing based on the host header names.

Although the documentation is quite exhaustive for skinning and classes and APIs, the installation and setup documents are a little obtuse, but how the hell can anyone complain, its open source and its a helluva piece of work! Thanks all.