Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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 ...One IP address and several domains on one install of DNN on the serverOne IP address and several domains on one install of DNN on the server
Previous
 
Next
New Post
6/25/2008 10:07 AM
 
Mahesh Anjani

Joined: 12/14/2006
Posts: 59

Hi,

 

Thanks for your quick reply.

 

I did not get your last comment “You could pull this off by simply putting the various headers into a single IIS site entry.” Can you please explain it in detail?

 

I have created three below web sites in IIS and point to the “main-portal” root folder. This root folder contains the “DNN” sub-folder in which I have installed the DNN.

 

  1. www.main-portal.com
  2. www.sub-portal-1.com
  3. www.sub-portal-2.com

 

When I try to access any of the above sites it doesn’t work as it points to the root folder of IIS not to the DNN site folder.

 

So I have to set portal aliases with below URLs. I have to type DNN to access the web site.

www.main-portal.com/DNN

www.sub-portal-1.com/DNN

www.sub-portal-2.com/DNN

 

How can I remove the “DNN” from above URLs? Is it possible to do it without changing the Web site pointer in IIS?

 

Thanks,

Mahesh
 
New Post
6/25/2008 5:22 PM
 
Will Strohl


Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

https://upendoventures.com
Joined: 3/1/2005
Posts: 2884

As long as there isn't anything unexpected going on in your IIS configuration, just changing the portal alias in your site might be good enough.  That is, if IIS is already looking for sub-portal.com and forwarding it to your DNN install (and not sub-portal.com/dnn), then all you have to do is this...

  1. Login as a host
  2. Go to portal settings
  3. At the bottom of the page add a new portal alias matching your domain name
  4. Navigate back to your site using the domain name only (sub-portal.com/Default.aspx)
  5. If needed, log back in as as host and delete the alias that includes the sub-directory

However, if you created those other sites as child portals, this may not work.

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
7/4/2008 1:54 AM
 
Mahesh Anjani

Joined: 12/14/2006
Posts: 59

Will Strohl wrote

As long as there isn't anything unexpected going on in your IIS configuration, just changing the portal alias in your site might be good enough.  That is, if IIS is already looking for sub-portal.com and forwarding it to your DNN install (and not sub-portal.com/dnn), then all you have to do is this...

  1. Login as a host
  2. Go to portal settings
  3. At the bottom of the page add a new portal alias matching your domain name
  4. Navigate back to your site using the domain name only (sub-portal.com/Default.aspx)
  5. If needed, log back in as as host and delete the alias that includes the sub-directory

However, if you created those other sites as child portals, this may not work.

Hi Will,

To access the portals we must have to type "DNN" in URL ex. sub-portal.com/dnn only then we get the dnn portal. I don't want to type "DNN" to access the portals that means sub-portal.com should be forwarded to dnn portal, but it's not happening.

How can I remove the “DNN” from above URLs? Is it possible to do it without changing the Web site pointer in IIS?

Thanks,
Mahesh
 
New Post
7/6/2008 12:43 AM
 
Will Strohl


Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

Will Strohl's Avatar

https://upendoventures.com
Joined: 3/1/2005
Posts: 2884

I see your dilema.  You should add the alias for the URL without "dnn" in it, then remove the other one.  However, if your have created the other portals as "child" portals, you may need to resort to using the URL Rewriting feature.  For instance, this may work:

LOOKFOR
(.*)/dnn/(.*)

REPLACE WITH
$1$2

Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
7/9/2008 3:04 AM
 
Mahesh Anjani

Joined: 12/14/2006
Posts: 59

Hi Will,

Thanks for your replay.

I have added portal alias www.main-portal.com, www.sub-portal.com etc without "dnn" but it's not working as desired.

Let me know you one of the important thing that was missed out in previous post that there is default.asp page under the main-portal root directory which redirects all requests to <Portal-URL>/DNN. 

Ex. When we request www.sub-portal.com (without "DNN"), default.asp redirects it to www.sub-portal.com/DNN. This has been done because if we request the www.sub-portal.com the request don't reach to DNN portal so to be severed it by DNN website, the default.asp redirects it to <PotalName>/DNN.

FYI: following is the directory structure of my web site.
I have created three below web sites in IIS and point to the “main-portal” root folder. This root folder contains the “DNN” sub-folder in which I have installed the DNN.

  • www.main-portal.com
  • www.sub-portal-1.com
  • www.sub-portal-2.com

    • All the sub-portals are created as parent portal. I have still not tried the second option as my portal using DNN 4.00.03 and Friendly Url is not available in this version. But as per my knowledge when you write Friendly Url rule, to look for (.*)/dnn/(.*) and replace with $1$2 though the page Url will show the <DomainName>/DNN/ .

    How can I remove the “DNN” from above URLs? Is it possible to do it without changing the Web site pointer in IIS?

    Thanks,
    Mahesh
     
     Page 2 of 3
    Previous123Next 
    Previous
    		 
    Next
    HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...One IP address and several domains on one install of DNN on the serverOne IP address and several domains on one install of DNN on the server


    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