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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Yet another Portal/Alias query!Yet another Portal/Alias query!
Previous
 
Next
New Post
8/29/2007 3:17 PM
 

dstefan@startrac.com wrote:

I too would like to setup my default DNN portal (created as a virtual dir named DotNetNuke in the folder c:\dotnetnuke) so that our intranet users can browse to intranet.mydomain.com.  I've added the alias to the portal's site settings list of aliases, and I followed MS article (190008) referenced above.  Browsing to intranet.mydomain.com brings up the under construction page, not the desired DNN page localhost/dotnetnuke.  Microsoft's article talks about adding the host header nanes at the default web site properties level, not at the virtual dir level (as far as I can tell, there is no option to set a host header name on a virtual dir).  I've tried just plain old intranet, intranet.mydomain.com, and intranet.mydomain.com/dotnetnuke as host header name entries.  All three take me to the under construction page, not the desired virtual dir page localhost/dotnetnuke.  Did I miss a step or two?

For you to access your site at intranet.mydomain.com several things have to happen.  First, your DNS has to have the intranet hostname in the mydomain.com domain pointed to the IP address of your DNN server.  Second, IIS has to be set to use the home directory of where your DNN installation is installed and DNN has to be installed at the root of that directory tree, not in a dotnetnuke subfolder or virtual directory.  Fortunately, this is all easy.  Once you have the DNS resolving to the correct IP address, create a new web site with the home directory of c:\dotnetnuke.  Copy the DNN  installation files to that directory.  Edit the web.config as needed for your database connection.  Then browse to http://intranet.mydomain.com/ and start your installation.  DNN will take care of the correct alias.

Forget installing by browsing to localhost as the instructions suggest and forget placing your install files in a dotnetnuke subdirectory and everything elose is fine.  :)

Jeff

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Yet another Portal/Alias query!Yet another Portal/Alias query!


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