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
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Do forwarded/masked domain names fool DNNDo forwarded/masked domain names fool DNN's portal alias system?
Previous
 
Next
New Post
6/13/2006 5:19 AM
 
Brett Anderson

Joined: 6/12/2006
Posts: 5

I've managed to successfully install DNN running on a GoDaddy-esque hosting environment and all seems to be running just fine (as far as I can tell anyways).  The problem that I'm running into, however, is having DNN recognize the two parent portals as seperate portals.  I have two domain names that point at the same directory (http://www.mydomain.com/dnn) but regardless of which domain I'm visiting that directory from, DNN only shows me the portal for the one.

Looking through the domain name registrar's system through which the two domain names are registered, I see that they are both being "Forwarded" to the correct domain and that the second domain is being "Masked" so that users will still see the correct domain even though it's sending the traffic to the other domain.  Does anyone know if these "Forwarded" domain names don't allow DNN to appropriate decide which portal to display to the users?  Do I need to go into the DNS records on the registrar's system directly and modify the A and C Names manually so that I'm circumventing the "Forwarding" mechanism?

Any suggestions would be greatly appreciated

-b-
 
New Post
6/13/2006 10:37 PM
 
Brett Anderson

Joined: 6/12/2006
Posts: 5

 

   OK, I have a slightly better feel for the concept of a "Forwarded" domain name vs. an "Aliased" domain name.  Please, if anyone has a better grip on this and could add your feedback, I'd appreciate it greatly.

   I appears as though most of the secondary domain registrar companies are offering up their free "Forwarding" service that can be added to your domain name via their online administrative tools.  The "Forwarding" basically takes users from one domain name to another.  For example:

   *   Domain Name #1:  http://www.I_WAS_REGISTERED_FIRST.com

   *   Domain Name #2:   http://www.I_WAS_REGISTERED_SECOND.com

   If you setup a hosting account and have domain name #1 setup to direct traffic there, it is "Aliased" to that hosting environment.  When you use a script in that directory to pull up the domain name, it will display "www.I_WAS_REGISTERED_FIRST.com".  Now, you go and register a second domain that you want to direct to the same directory, only you use their free "Forwarding" service.  You type in "www.I_WAS_REGISTERED_SECOND.com", but the script on the page will still display "www.I_WAS_REGISTERED_FIRST.com".  The cheap part about the whole process is that it seems that most of the hosting companies' "economy" hosting packages don't allow you to "Alias" multiple domain names to a single hosting point.

   So, when I use domain name #1 and look at the DNN portal that's setup for it everything seems to work just fine.  I type in "www.I_WAS_REGISTERED_FIRST.com/dnn" and I get taken to DNN Portal #1.  However, when I type in domain name #2, "www.I_WAS_REGISTERED_SECOND.com/dnn", I still see DNN Portal #1.  All of the DNN portal aliases are correct, but the DNN script seems to see them both as coming from the same domain name because of the "Forwarding".

   Can anyone double-check me on this?  I can't get anyone on the host's tech support line to give me anything but a confused silence on the other end of the phone.  And they certainly make no attempt at assisting with the DNN application.  I'd really like to keep the "economy" hosting price, but still have multiple domain names pointing at DNN and displaying their correct portals.  Suggestions?

-b-
 
New Post
6/15/2006 3:10 AM
 
Brett Anderson

Joined: 6/12/2006
Posts: 5

OK, now I'm in a real jam.  The host that I'm using here (XSiteReg.com) doesn't allow multiple domains to be aliased to a single Windows hosting account.  So unless I can figure out a way to get DNN to recognize a "Forwarded" domain name and alias it to the correct portal there's *no* way to setup more than one portal per instance of DNN in their hosting environment.

Please... *anybody*!  If there is a way to have DNN recognize a "Forwarded" domain name I'm in dire need of the suggestion.  Otherwise the 11.75 months of my 12-month hosting contract that I just got into is going to be worthless as I'm going to have to switch to another provider who allows multiple domains to be aliased directly to a single hosting location.  HELP!  PLEAD!  BEG!  :)

Thanks.

-b-
 
New Post
6/15/2006 4:03 AM
 
Nina M


www.berrydigital.com.au
Joined: 1/23/2004
Posts: 1961

Did you get an IP address allocated - I think (and this is just a think OK) you should be able to setup a wildcard entry - and try pointing you dns www records to that IP - and see how that goes.. Maybe DNN will pick it up - but I feel that it really needs the IIS entry in there too, so you're stuck.

But to be honest, if someone has set up only one account, it doesn't sound very positive.I'm trying to think if by having your own IP address and the ww records allocated would make a difference or if you really do need to put them into IIS.

Based on this nightmare - I'd be moving to another provider.. and read the fine print.. I hate seeing people caught out like this since it's not really the fault of the hosting company if that's their policy - but nevertheless a nuisance.

Nina Meiers

Nina Meiers My Little Website
If it's on DNN, I fix, build, deploy, support,skin, host, design, consult, implement, integrate and done since 2003.
Who am I? Just a city chic, having a crack at organic berry farming.. and creating awesome websites.
 
New Post
6/15/2006 5:06 AM
 
Brett Anderson

Joined: 6/12/2006
Posts: 5
nina wrote

Did you get an IP address allocated - I think (and this is just a think OK) you should be able to setup a wildcard entry - and try pointing you dns www records to that IP - and see how that goes.. Maybe DNN will pick it up - but I feel that it really needs the IIS entry in there too, so you're stuck.

But to be honest, if someone has set up only one account, it doesn't sound very positive.I'm trying to think if by having your own IP address and the ww records allocated would make a difference or if you really do need to put them into IIS.

Based on this nightmare - I'd be moving to another provider.. and read the fine print.. I hate seeing people caught out like this since it's not really the fault of the hosting company if that's their policy - but nevertheless a nuisance.

Nina Meiers

   Thank you Nina very much for the reply (great tutorial videos too, FYI).  I've tried playing around with the DNS records for the domain names, but the problem lies with the hosting side of things.  IIS needs to have the website/directory setup to be looking for all of the appropriate domain names in order for them to get picked up and I've just gotten verification from my host that they do *not* allow that kind of multiple-domain aliasing to occur in their environment.  So I'm fairly well stuck there.

   I also just got off of the phone with the tech support line for GoDaddy's hosting service and they are telling me the same thing.  They say that only one domain name can be directly aliased to any one windows hosting account.  I've seen many people posting on here about using GoDaddy for their hosting provider.  Is anyone out there who has successfully aliased/forwarded their multiple domains to work with DNN under GoDaddy's system?  Or does everyone purchase a seperate hosting account for each DNN portal they create?

   Please let me know if this is possible or if I'm stuck looking for another provider.  Thanks again.

-b-
 
 Page 1 of 4
1234Next 
Previous
 
Next
HomeHomeGetting StartedGetting StartedInstalling DNN ...Installing DNN ...Do forwarded/masked domain names fool DNNDo forwarded/masked domain names fool DNN's portal alias system?


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