Hosting multiple domains against same site

Vote:
 

Hi Everyone,

 

We have a requirement to host a single website, and have it accessible using 2 domains:

 

  • http://www.ourpublicdomain.com/

and

  • http://ourprivatelyaccessibledomain.com/episerver/cms

 

We have a load balancer standing in front of our 2 appservers, that will deny any request to http://www.ourpublicdomain.com/ with the word 'episerver' in the URL.

It will allow requests from the privately accessible domain that is only accessible within the confines of our corporate network - the idea being we want to restrice editorial access to the website to only people within the corporate network using the internal-only accessible URL.

 

Is there a way to achieve this via Site management in the CMS? I've tried the following:

  • Create a single site, with URL set to http://ourprivatelyaccessibledomain.com, and additional host of www.ourpublicdomain.com
    • The problem with this approach was that although CMS editing worked fine, the additional host www.ourpublicdomain.com did not pick up the start page of the site.
  • Create a single site, with URL set to http://www.ourpublicdomain.com, and additional host of ourprivatelyaccessibledomain.com
    • The problem with this approach was that although the start page worked fine for the public domain, all links created in the editorial interface within CMS used the public domain, even if the CMS was accessed via the privately accessible domain URL.
  • Create 2 sites, one with URL set to http://www.ourpublicdomain.com/ with start page pointing at my intended page in the tree, and another site with URL set to http://ourprivatelyaccessibledomain.com with start page pointing at a sibling page of the public start page.
    • The problem with this approach was that as soon as any pages underneath the start page of the public site were clicked in the CMS, the URL changes to the public site.

 

Is this indeed at all possible configuration in the CMS, to have 2 different domains pointing at the same site, one for internal content editing, and one for public access?

 

Please help!

Dan

#82576
Mar 14, 2014 16:10
Vote:
 

Well, the expensive solution is to have a separate server for edit/admin (more secure but also additional hosting cost...remove edit/admin capabilities from public server).

Your solution will probably work as well. Check IIS host headers settings...

#82581
Mar 14, 2014 17:39
* You are NOT allowed to include any hyperlinks in the post because your account hasn't associated to your company. User profile should be updated.