I want to deploy our production server so that our DNN installation is accessible via our domain name (for example
www.ourdomainname.com). We originally installed DNN into a subfolder/virtual directory on our development VM's.
I somewhat understand the concept of installing DNN into the root of IIS 6 as I needed to do this for our pre-live site which is hosted on GoDaddy.com. However, I am prepping our production server that we will be hosting at our own data center. I am curious as to the best way to configure things to properly work with the respective DNN alias(s) (i.e.
www.ourdomainname.com, domainname.com, etc.). At the moment we have to key/see the directory structure in each URL path and my alias of
www.ourdomainname.com is dropping me at the IIS's root folder 'under construction' page (as I would expect).
Is it best to attempt to move the site into the default websites root folder of IIS 6, change the configuration of the default website, create a new website in IIS 6 and use that, ?, ?, ?
Looking forward to hearing some thoughts and good recommendations!
-Todd