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

HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Parent portal alias problemParent portal alias problem
Previous
 
Next
New Post
9/3/2008 5:37 PM
 

I have a DNN system that was set up by an outside vendor that I'm now maintaining. I'm having difficulty getting a new parent portal to show up correctly.

The host settings have the following:

/site
D:\WebSite\site

My system is setup so that the www site has 2 aliases

http://65.x.x.x/site

http://www.website.com/site

DNN does not give me the option of deleting the 65.x.x.x alias. It will only let me delete the www alias.

IIS is set with virtual directories to send www.website.com to the IP address. There is also a default.aspx in the root directory that does a response.redirect to www.website.com/site.

The www site works fine.

However, I created a new parent portal called brands.website.com with a home directory of brands, a new administrator account and used a portal template I exported from our main site. I created an HTTP alias for the portal for brands.website.com

The DNS is set to go to the IP address of the DNN server. We then set IIS to send brands.website.com to the straight IP address. That got us redirected to the main site, presumably because of the root default.aspx. So, we set IIS to send brands.website.com to 65.x.x.x/site. When I type brands.website.com into my browser, I'm redirected to 65.x.x.x/site, not my new portal.

What am I doing wrong? I really don't want to make a child site.

 

 

 

 
New Post
9/3/2008 11:26 PM
 

First off, if you want to change http://65.x.x.x/site to something eles you can do so in the PortalAlias table.   After changing this you will want to restartthe site.

The default.aspx page that redirects to www.website.com/site I don't believe is part of Dotnetnuke and should be eliminated.

Normally,

Creating the parent portal and setting the portalalias for the parent portal is correct.   Pointing the DNS to the IP Address assigned to the DNN site is correct, so I think those first two things need to be resolved and then you will start having some luck.

Keep us posted.

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
9/4/2008 2:51 AM
 
  • you can delete any alias except the one, you are currently using yourself. Login with www.website.com and remove the ip access. this shall solve the problems with 2nd parent portal as well.
  • for parent portals, you should use IIS websites, not virtual directories.

Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
9/4/2008 5:14 PM
 

thanks for the help, particularly the point that I have to login to the other portal to remove the IP access. It's still not working quite right, but I think that has to do with the way our IIS is set up. We pointed the home directory to the root instead of the DNN directory. When we try to point it directly to the DNN directory, we're getting some weird results, but I don't think that's DNN.

 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Parent portal alias problemParent portal alias problem


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