Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...Installing on eventual production serverInstalling on eventual production server
Previous
 
Next
New Post
10/21/2010 10:28 AM
 
Mark Williams


Joined: 10/5/2010
Posts: 170
We're looking at moving to DNN (probably Professional) and I would appreciate some pointers around installation.

We have a live site running on plain vanilla ASP.Net right now. Let's say that is at www.company.com. We have two cloud servers, one for the production server (www.company.com) and as a secondary/backup server (www2.company.com).

What I want to do is install and configure DNN on the second server, get it to the point where it's ready to roll out and then switch my DNS entries so that www.company.com now points to the secondary server and www2.company.com points to the old primary server. When I have this done (and the DNN server has been validated in production) then I'll move the secondary server to DNN too.

What I am not clear on is how I should install. I see references to using the FQDN of the server when I install. For me, this will initially be www2.company.com but will eventually switch to www.company.com. Is there any problem with installing to the www2 name and the switching to www?

Thanks.

Mark
 
New Post
10/21/2010 2:52 PM
 
Carlos Rodriguez

www.almacigo.com
Joined: 6/10/2003
Posts: 615
Mark:

From what you have said I presume that you only have one of the servers in production and the other is just a warm, stand-by backup.  In other words, they are not a true server farm.  If that is the case, then I may be able to give you some pointers, if they are a true server farm other complexities are involved.

All you want to do can be easily accomplished by manipulating the IIS Host Header for the new DNN site and the alias of the site inside of the DNN settings.  You can start with something like www.companydnntest.com and later change it to the production domain when you are ready.  Then the third part to make the new site work on the temporary URL (host header/alias combination) is how to reach the site via DNS.  This you can fake by making an entry on your PC Hosts file.  When you go to production with the new site remember to change or remove the host header for the old site so that IIS does not get confused.

These are just the major concepts involved.  Post if you need more details.

Carlos
 
New Post
10/21/2010 3:50 PM
 
Mark Williams


Joined: 10/5/2010
Posts: 170
Thank you, Carlos, and yes you are correct about this being a non-web farm setup. A further clarification....

My current DNS points to www.company.com and www2.company.com. Since that is aready available what I'd like to do is bring up my initial DNN deployment on www2 and when I am done switch things so that it becomes www. Do the steps you describe work just as well for the HOST (www and www2) as for the domain? I think I am missing exactly what it is that configured within DNN itself - is it the fully qualified domain name of the server or just the domain?

Thanks.

Mark
 
 Page 1 of 1
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Installing on eventual production serverInstalling on eventual production server


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