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 ...Parent Portal, Alias, domain issuesParent Portal, Alias, domain issues
Previous
 
Next
New Post
8/22/2007 12:04 AM
 

Background: Windows Server 2003, DNN 4.05.05

If I type in www.mydomain.com it shows me the default web site, not the DNN portal.

If I type in www.mydomain.com/dotnetnuke, it redirects me to localhost/dotnetnuke which is the main original portal of DNN, not the new portal I setup.  The new portal I setup has www.mydomain.com as an alias.

Why does it redirect to localhost/dotnetnuke when I attempt to open www.mydomain.com/dotnetnuke?  Hence I can't access my new portal at all.

 
New Post
8/23/2007 12:36 PM
 

I had the same problem.  Under site settings, at the bottom is Portal Aliases.  Add mydomain.com/dotnetnuke to the list.  I have the ip version in there as well just in case.  Although it does not seem to affect it, I have localhost/dotnetnuke in there as well.

 

I've been trying to use the dotnetnuke dir as the default so that you don't need to type it, so just www.domain.com would show that vdir.  However, it doesn't want to work when I just specify it as a website not a vdir; in IIS it seems that the root site cannot come from a vdir.  There has to be something easy that I'm overlooking to get this to work without a http redirect page.  Have you gotten this to work?  I've been searching the forum and documentation for sometime as well as googling iis but can't seem to get a straight answer that works...  Much obliged if you have an idea....

 
New Post
8/23/2007 11:39 PM
 

I got the site up and running.

As to your question regarding not having to enter "/dotnetnuke" to the URL, I found two solutions, neither of which I like.  One is that you put the DotNetNuke files right into the root directory of IIS.  The other is to create an ASP page that does an If Then or Select Case to redirect the user to the "/dotnetnuke" if it's a certain domain.  If it's not, then it will show the default doc in the root.

I have a Win 2003 Server so I can have multiple websites.  I'm trying to setup a website (not virtual directory) and load the DNN files in the root of that website, but I haven't gotten that to work yet.  This would eliminate the redirect or having to load the DNN files in the root of the default website.  If you're running on XP, you only get the one default website, so you'll have to work the redirects or install the DNN files in the root.

Anyone have any comments on my statements?  Is this correct?

 
New Post
6/2/2008 5:27 PM
 

FYI for anyone who still didn't get this.  I had the same problem, fresh install, everything went to localhost/dotnetnuke.  It seems the Portal Alias setting is picky.  For example, I put in www.mydomain.com/dotnetnuke/ and that wouldn't work at all.  But as soon as I put it mydomain.com/dotnetnuke (no extra slash) it worked perfectly.

 
New Post
6/2/2008 5:27 PM
 

FYI for anyone who still didn't get this.  I had the same problem, fresh install, everything went to localhost/dotnetnuke.  It seems the Portal Alias setting is picky.  For example, I put in www.mydomain.com/dotnetnuke/ and that wouldn't work at all.  But as soon as I put it mydomain.com/dotnetnuke (no extra slash, no www) it worked perfectly.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Parent Portal, Alias, domain issuesParent Portal, Alias, domain issues


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