Hello,
DotNetNuke has the concept of virtualised portals i.e. multiple different portals (each with their own set of pages, users, look & feel, functionality etc.) can share a single database. To determine what portal to direct to DotNetNuke looks up a list of portal alias's and redirects accordingly. This means that theres a lot of flexibility in this area.
1. yes, you simply create a portal with one name (e.g. mysite.com) and add a portal alias for it (e.g. thesite.com)
2. yes
3. you can do this by having seperate portals for each address - if you only want to change the homepage it would take an additional piece of logic e.g. a simple skin object that updated the skin based on url fragment
4. yes they are - in some cases they will change e.g. if you have an SSL site mapped and have enabled SSL in DotNetNuke - as it needs to be domain specific a redirect will occur.
5. add entries into your hosts file -
http://kb.mediatemple.net/questions/6...
6. search is user/role permission specific by default - as users are portal specific (except host) it means searches are portal specific. It's easy enough to create a custom search provider to search across multiple portals , or buy one off snowcovered.
7. yes - there are already a number of options such as active directory, facebook, moodle etc., and it's easy to write custom ones
http://www.adefwebserver.com/dotnetnu...
Cathal