Products

Solutions

Resources

Partners

Community

About

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...One WebServer - Many PortalsOne WebServer - Many Portals
Previous
 
Next
New Post
12/20/2008 8:44 AM
 

Hi,

I need a recommendation.

I have a server with IIS7, I registered few domains and I'd like to run all the sites (per doamin) with DNN.

 

What should be a right setup?

A. 1 site in IIS7 (per domain) + Host Header set + 1 DNN per domain

B. 1 site in IIS7 (per domain) + Host Header set + 1 DNN per server

C. 1 site in IIS7 per server + 1 DNN per server

 
New Post
12/20/2008 8:59 AM
 
  • you can install as many DNN installations as resources available on your server
  • you will be able to install more portals, if they share a single installation
  • shared installations cannot be restored individually.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
12/20/2008 9:14 AM
 

Leupold,

 

When you speak about installing "more portals", you're meaning to manage 1 IIS web site with DNN installed, and setting [a host header + portal] for each domain correspondingly ???

Just to clarify what I'm asking for:

Let's say I have d1.com and d2.com registered. DNS resolves both names to the same IP address. There are other domains realted to the same IP (so I need host headers). Just for the sake of the case, I have no problem with server's resources.

What I'd like to get is as following - d1.com goes to "Portal A", d2.com goes to "Portal B"

 

What should be the reasonable deployment scheme?

 

 
New Post
12/20/2008 10:39 AM
 

Although DNN supports having multiple portals per installation I'd shy away from that if they are not related, that just makes it harder (not impossible) to backup/restore individual portals if you wanted to move them. 

I tend to set mine up as separate installations (so different SITES in IIS 7 with different IP addresses internally associated with them).  If you don't have the power to internally assign a new IP address that maps to the external address of your domain, then the host header method works fine as well.  I also go a step further as to separate them into their own application pools so they don't conflict with each other for any reason -- ie., if one crashes its app pool it doesn't bring the other ones down as well.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
New Post
12/20/2008 1:51 PM
 

regardless, if you are using a single installation or separate installations per portal, you will use host headers to direct the sites appropriately (as long as you don't use SSL, which requires a separate IP per (domain specific) certificate).


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...One WebServer - Many PortalsOne WebServer - Many Portals


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out