First thing is you will need either access to add a dns entry if you want a parent portal (one that uses a different dns entry).  There are two types of portals available one is a parent.  This would be similar to http://myportal.mydomain.com  (this will require you to have a dns entry) .  The second is a child portal that would be similar to http://www.mydomain.com/myportal (this requires no dns entry).

As far as setting them up from DNN you simply choose which type you want.  The rest is pretty straight forward.  If you need more direction I will try to be more specific.

Russ

Russ

I am a bit leary of having DNN manage my top domain's through a single install.  That being said part of that being leary is the issues that would be involved with IIS and host headers and dns entries.  That being said you could test locally by creating to seperate host file entries like domain1.tst and domain2.tst make sure they both point to the local machine.

Once you have done that then you could go through the install process and set up domain1.tst, then create a new portal.  As far as the type I would probably suggest using a parent portal.  (the problem here is that you would need another host file entry i.e. portal.domain1.tst again pointing to the local machine)  once you have done the portal set up and the host file ste up, navagate to portal.domain1.tst.  Then go to the admin > site settings  at the bottom in the portal alisa area I woul enter domain2.tst.

This is probably as close as you can get to proof of concept without a Windows server a second domain and the dns records in a live enviroment.

Let us all know how that works.

Russ

Russ