Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

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 ...Multiple Portal Strategy in Shared Hosting..Multiple Portal Strategy in Shared Hosting..
Previous
 
Next
New Post
6/26/2007 1:51 PM
 

I have been running this for a while now and wondered if there were better, less expensive ways:

To have 2 or more domains in one shared hosting arrangement provide the dnn codebase for other domains, i am currently leasing one static IP per dnn codebase, to ensure each parent portal can find the correct source of its' site. This works, but costs money.

I have stayed away from a coding approach, but just wanted to revisit this as i am "shaking things up" a bit.

What is everyone else doing? A separate codebase per domain is not a great solution for me as this increases disk cost, 3rd party control cost etc.

thanks for any thoughts, drew..

 
New Post
6/26/2007 3:35 PM
 

Drew, depends on what you can do with the hosting package and then what you want. 

You don't need to have a unique IP per parent portal. IIS host headers allows for multiple domains and IIS sites to share a single IP, so you can even have multiple DNN installs sharing a single IP.

If you are talking about a lot of small Sites it might be a better use of resources to place them in a single DNN install and a single IIS site.  You can always move these off to thier own IIS site/IP combo later (still using the single DNN install) if you want to use thier own SSL cert for example.

With larger sites that have a lot of custom modules you might want to keep them in thier own DNN install.

HTH

Antony

 

 
New Post
6/26/2007 5:14 PM
 

thanks Antony.. perhaps it was just a limitation of a prior host, and if memory serves, for me to have 2 or more codebases in the same hosting package, sharing an IP address, they said.. no no, no can do, you need a separate IP per codebase. So what you are saying is simply use IIS to direct the parent portal back to the codebase url via headers. As long as the end-result url displayed within the browser is the original destination and we maintain uniqueness to allow for proper email etc... then great..

 
New Post
6/26/2007 6:27 PM
 

The host headers don't really 'redirect' in IIS, they are more a filter to allow multiple sites to share a single IP address.  And yes the original URL will be retained unless something changes it.

Antony

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Multiple Portal Strategy in Shared Hosting..Multiple Portal Strategy in Shared Hosting..


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