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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN, Mulitple Portals and Amazon AWSDNN, Mulitple Portals and Amazon AWS
Previous
 
Next
New Post
2/6/2013 8:56 PM
 

I am moving several sites from a dedicated server over to Amazon AWS and so far everything is great. I have a couple different DNN installs each with a single portal/site on my EC2 instance so far and they work great.

Next to move is a DNN install that has 3 separate sites/parent portals on that one install. I have not tried to move it yet, and think I may have a problem with the multiple sites on one dnn instance because a single EC2  instance only has one IP address, and that isn't even the same as the elastic IP I am using. I believe this install is older - probably dnn 5.x.

Since I cannot use a separate IP address for each dnn instance/website I am using the host name part in IIS which works fine for the single site dnn installs, but now that I need to do a multiple site dnn install I don't see how it will work - what will I put in the host name in IIS?

hmm... I wonder if I can create a new site in IIS for each parent portal, set their host name to the site name and then have it point to the same folder that has the one install. That almost seems like it will work.

Sorry to ask questions before actually trying, just hoping someone knows if it can be done before I give it a try tomorrow.

Server is win 2012. IIS 8

 
New Post
2/7/2013 10:30 AM
 
DNN doesn't need multiple IP addresses, DNN handles the portals based on the ALias, so as long as you have the Aliases defined as BINDINGS in IIS (www.domain1.com, www.domain2.com) then you should be good to go.

If you have aliases for the old IP addresses I would simply remove those and make sure DNN has aliases for the domain names.

Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
2/7/2013 11:55 AM
 
ah, I see that now... excellent! Thanks, I sort of had seen the bindings part in IIS but hadn't really figured out that was what I needed.
 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...DNN, Mulitple Portals and Amazon AWSDNN, Mulitple Portals and Amazon AWS


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