This procedure describes at a high level how to configure a web farm for DNN. This web farm setup is best suited for an application with 1 or a few distinct sites which
receive a high volume of traffic. Each web server serves all configured websites. The
number of webheads depicted is just an example.
Assume your DNS server (not in this diagram) is configured in the following way
DNS server (18.104.22.168) with the following DNS records
(Please note this sample is assuming you have only one portal on your DNN Installation)
LOAD BALANCER (22.214.171.124) has a binding for www.mydomain.com
WEBSERVER1 (126.96.36.199) has a binding for webserver1.mydomain.com
WEBSERVER2 (188.8.131.52)has a binding for webserver2.mydomain.com
SQL SERVER (184.108.40.206) has a binding for dbserver.mydomain.com
FILESERVER (220.127.116.11) has a binding for fileserver.mydomain.com
1. Set up the Loadbalancer to distribute traffic coming from www.mydomain.com into webserver1.mydomain.com and webserver2.mydomain.com
2. Use UNC for file sharing, Using a file share ensures that files used by the DNN application are always the same (and in sync).
3. Install DNN on WEBSERVER1, once completed, you will have your DNN setup for a single server.
4. Install the WEBSERVER2 by adding a new Website to IIS and pointing it to UNC share and using the already configured DATABASE on DBSERVER.
5. Add the following aliases to your Portal.
Note that only www.mydomain.com should be exposed to the external world as webserver1.mydomain.com and webserver2.mydomain.com are only accessible internally.
Confirmation: With these steps completed, whenever you create a new page to that portal or add a file or asset, it will be saved without the server URI, allowing that all aliases can reach that page/resource just like a normal web request.
Additional Note: For more information on setup details and other potential scenarios, please review attached PDF files for versions of 9.X.X. and Version 4.1.