Well I have a question in regards to Active Forums and DNN6.

Is this possible to have one DNN installation with one ActiveForum installation and then have two Portals with share this activeforum installation, but having the option of both shared forums, but also forums only visible on one of the two portals.

I want to have the same fora in two different websites (different domains). One site (site one) is open to everyone (indexed by Google). The other site (site two) is basically located on an intranet, people needs first to login to their AD account  before they can access the site. Most of the different forums are open to both sites and it must be possible to post and reply from both sites, but other fora are only active and visible for all users on either site one or site two.

But is this even possible with DotNetNuke and Active Forums?

/Erik

I am sorry but the forums module does not support that configuration.

Oh - so what is possible with the forums module? Nothing of the above?

Thank you Ben. But can you eventually tell me if nothing in my request is possible, or if some of it is possible. I didn't think that the request was way out.
/Erik

You can have the forums module on multiple portals, but it keeps the data separate.

Ok thank you.

Then my follow-up question might not really be ActiveForums related. But I would love to know if it's possible with DotNetNuke to have two different domain names going into one portal. As far as I remember, then this is possible. But is it then possible to assign a different set of skins/containers to each domain name?

This could actually solve most of the issues I have above.

You can indeed have more than one URL pointing at one DNN portal. Just add the appropriate IP address to your domain and add the alias to portal aliases for your DNN instance. That said...if this is a public site and SEO is important to you this is considered bad SEO practice (duplicate content)

As far as the skin per url this would likely be something custom...perhaps a skin object or module that looked at the page referrer and over-wrote the skin being loaded on the page.

As I'm also currently looking into using Ifinity URL Master to handle the HTTP redirections (to match my old site) I found that it actually looks like URL Master can handle the part of using different domains on the same portal but with different skins. In terms of SEO, then there will be no duplicate content as only one of the domains is public. And even if it was, then it should be possible to handle through URL Master also by using canonical tags.

/Erik