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 ...Host headers not resolving to Intranet DNN InstallHost headers not resolving to Intranet DNN Install
Previous
 
Next
New Post
4/17/2007 11:45 AM
 

I've installed 4.5.1 on our company Intranet, a clean installation using the Auto option from the wizard.

The site is browsable locally on my web server using http://localhost/DotNetNuke4

However, though I've added new http aliases for my site, like test.mydomain.com, the portal does not open when that value is placed in a browser locally on the web server or on another machine on my domain.

The Host (A) value has been added via DNS on my domain controller, to point to the correct IP address on my network.

I've got a few other sites running on my web server, but this one just isn't resolving in a browser using the http headers.

I'm getting an Under Contruction page...  this is the specific error that shows in my browser window:

The site you are trying to view does not currently have a default page. It may be in the process of being upgraded and configured.
Please try this site again later. If you still experience the problem, try contacting the Web site administrator.
--------------------------------------------------------------------------------
If you are the Web site administrator and feel you have received this message in error, please see "Enabling and Disabling Dynamic Content" in IIS Help.
 

Other than that, everything is fine.  Suggestions?


Chad Voller -- MCP, DNN Aficionado
Leapwise Media
View my View Chad Voller's profile on LinkedIn
 
New Post
4/17/2007 1:07 PM
 

The message you posted is telling you that your request is getting to the server, to IIS, but that IIS cannot find the site in question.  In other words, it is IIS that cannot resolve "test.mydomain.com" to an actual Web site.  What I think you are missing, is the Host Header for the site.  Add the Host Header to the site, it needs to be just like you wrote it, test.mydomain.com.  Then, you also need to enter test.mydomain.com as an Alias for the DNN portal in question.  You can do that logging in as Host at the server or editing the table PortalAlias directly in the database.  If you do it directly to the database pay attention to the PortalID value if you have multiple portals.

That should work, I do it all the time.

Carlos

 

 
New Post
4/17/2007 1:18 PM
 

Ok, well, I'm a bit confused... but it's working now.  I added a new site in IIS and pointed it to the home directory of DNN and gave it the appropriate header values... however...

The last time I installed DNN on my webserver, I used VWD Express and used HTTP instead of file system... When I did this, I did not create a "New Web Site" in IIS, I simply pointed DNS to the IP Address of the web server, gave DNN the correct Alias, and it worked.

Or maybe I just have a bad memory.  :-)


Chad Voller -- MCP, DNN Aficionado
Leapwise Media
View my View Chad Voller's profile on LinkedIn
 
New Post
4/17/2007 1:27 PM
 

You were probably running that instance of DNN from the "Default Web Site".  In that case, you could have added the new Host Header to that Web site definition and it should have worked.  Bear in mind that one Web site can have multiple Host Headers, that is actually how DNN can host multiple portals, responding to different URLs (or domains) with one physical installation.

Also, sometimes, after making changes to IIS, you just need to do an IISReset to make sure that all changes kick in.

By the way, not that it matters much now, but you do not need VWD Express to install DNN and it is actually not part of the installation process.

Carlos

 

 
New Post
4/17/2007 1:31 PM
 

Thanks for the help Carlos!

The installations I did today were completely just by using the install.zip files and IIS.  I have removed VWD Express from the picture. 

All is well...


Chad Voller -- MCP, DNN Aficionado
Leapwise Media
View my View Chad Voller's profile on LinkedIn
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Host headers not resolving to Intranet DNN InstallHost headers not resolving to Intranet DNN Install


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