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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke mothership a little unstable?DotNetNuke mothership a little unstable?
Previous
 
Next
New Post
8/26/2006 3:57 PM
 

John Mitchell wrote

One way around this would be to setup a seperate IIS website using only one worker process that points to your same DNN install and use that for administration.

John, can you explain this a bit more? Currently I have one site setup that points to the folder where DNN is installed and that site has host headers. How can I setup a second site that points to the same folder? Do I need to remove the host headers from both sites? I really do not see how this would work.

 
New Post
8/26/2006 4:30 PM
 

If you already have an IIS site pointing to your DNN install folder and you are using Host Headers in IIS then you will need to either use a different IP address for the administrator site, or use a different Host Header on the new IIS website.

If you use a different Host Header, then you will need a PortalAlias setup to handle that in DNN.  Call it something like "admin.smallbizserver.net"

Just as a refresher, or for those who may not know :
Host Headers in IIS are used to determine the IIS website being requested when more then one IIS website shares the same IP address. 
The PortalAlias is used by DNN to determine which Portal in the system is being requested, which happens after IIS has determined which IIS website is handling the request.

 


DotNetNuke Modules from Snapsis.com
 
New Post
8/26/2006 4:49 PM
 

Thanks John. I have a range of static IP addresses so I have the possibility to use more then one. I understand I can setup multiple site on different IP addresses without host headers and running on the same port. Been there, done that. But I would do the following:

Site A in IIS has IP address 82.94.217.243
Site B in IIS has IP address 82.94.217.244

Both sites points to the folder where DNN is installed. Currently I have a host A record 'www' for smallbizserver.net setup that points to 82.94.217.243. Can I add another host A record for 'www' and have that point to the second IP address? I doubt that this is possible? I have never seen two of the same host A records point to different IP addresses or am I completely wrong? And if this is possible do I need to do anything in the web.config or session state storage?

 
New Post
8/26/2006 5:27 PM
 

Ok, lets step "above" IIS into DNS. 

Yes, you can have two (or more) A records with the same host name that point to different IP addresses.  This is how some people setup Round-Robin DNS which lets your DNS server take turns handing out IP addresses when requests come in.  If those IP addresses were actually on different machines then you could get a cheap load balancing that way.

But in this case we want them to go to different  IIS websites which can also be on the same machine.  If they are using the same hostname then DNS will not know which IP address you really want and it will just give you the next one that matches your domain lookup.  So you still need another hostname to make sure you get to your administrative portal. 

Then again, you could just skip DNS and put the IP address into the browser directly, in which case you'll need a PortalAlias to match the IP.

By the way, if there are a lot of updates being made to your site by content editors, etc.  This is a good idea regardless of if you are using Web Gardens or not.  The reason being that if you are doing administrative tasks you will generaly be tying up the thread your request is on for longer amounts of time.  So if you had a seperate set of threads for admin and normal browsing your normal browsing users will see better response times.

Of course that last point also becomes moot if you are doing Page Caching. :)

 

 


DotNetNuke Modules from Snapsis.com
 
New Post
8/26/2006 5:42 PM
 
Hmmm, I don't get it. My site is on www.smallbizserver.net and not something else. So, how can I benefit of two instances in IIS when one needs another hostname? BTW, is that host name in the host headers you are writing about or in DNS? Or should I setup those two IIS instances without host headers and only on different IP addresses? And how do I get 50% traffic on each instance???
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DotNetNuke mothership a little unstable?DotNetNuke mothership a little unstable?


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