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 ...Configuring IIS for Multiple Domains/PortalsConfiguring IIS for Multiple Domains/Portals
Previous
 
Next
New Post
11/14/2006 7:41 PM
 
How to do i configure IIS for multiple portals/Domains.

I and working on 2 different portals that have different  domain names (ei.  www.mydomain.com www.mydomain2.com).

I also need access them locally from the server and my workstation.

I bought the "Professional DotNetNuke 4 book which said (on Page 86) in the section on setting up parent portals that you need to configure IIS "Which is outside the scope of this book".

Thanks
 
New Post
11/15/2006 3:45 AM
 
in your web site settings, there is the assignment of IP addresses to the site. You can also add host header values - meaning the server.domain values to separate domains. Leave host header blank to catch all domains assigned to the IP. Additionally you need to assign the server.domain values to IP in your name server.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
11/15/2006 6:08 AM
 

Hi,

I also would like to know what the best way is to set up the IIS for several different domains pointing to the same portal. Here are the steps i've taken so far....have I missed something? I have:

  • windows server 2003 standard (2.8 GHz, 2.0 GB of RAM) 
  • asp.net 1.1.4322 ánd asp.net 2.0.50727 installed
  • MS SQL server
  1. setting up a directory with full control on user NETWORK SERVICE
  2. create an IIS web (ASP 2, cause its DNN 4.3.5)
  3. creating its own Application Pool with the following properties:
    1. Recycling:
      1. recycle worker pocesses after 1740 minutes (should maybe be once every night?)
    2. Performance:
      1. shutdown worker processes after being idle for 2000 minutes
      2. limit the kernel request queue to 4000 requests
      3. webgarden: maximum nuber of worker processes: 10 (I dont think I have enables this in the web.config...what ate the possibilities of this?)
    3. Health: No changes
    4. Identity: Predefined Network Service
  4. installing DNN 4.3.5
  5. adding the domains to the host portal (Host >> Portals)
  6. creating an IIS website for each domain in order to have seperate statistics
  7. adding the host header values in each IIS web
  8. each IIS web points to the same application pool
  9. I use HTTP compression
  10. I use pageblaster
  11. I reduced the log viewer in logging only
    1. SCHEDULER_EXCEPTION
    2. GENERAL_EXCEPTION
    3. MODULE_LOAD_EXCEPTION
    4. PAGE_LOAD_EXCEPTION
    5. SCHEDULER_EVENT_FAILURE
  12. in the schedular I have only:
    1. DotNetNuke.Services.Scheduling.PurgeScheduleHistory
    2. DotNetNuke.Services.Log.EventLog.PurgeLogBuffer
    3. DotNetNuke.Services.Search.SearchEngineScheduler

Now I run 5, and still increasing, subportals but I find the performance not optimal. Any extra feedback/input is much appreciated!!

Keston

 
New Post
11/27/2006 11:06 AM
 
bump!
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Configuring IIS for Multiple Domains/PortalsConfiguring IIS for Multiple Domains/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