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 ...portal alias testing/productionportal alias testing/production
Previous
 
Next
New Post
2/17/2015 2:28 PM
 

HI guys:

 I'm about to take my first DNN 7 site and go live. We've been developing it using the hostname that our hosting provider has given us. Temphost.myhostingserver.com 

FOr testing, I went in to the Site Aliases and added an alias. i put it as www.mycompany.com

 I edited my C:\windows\system32\drivers\etc\hosts file and made an entry WWW.MYCOMPANY.COM that points to the IP of the temphost.myhostingserver.com

 I browse to the site using WWW.MYCOMPANY.COM and get: Web Page is Unavailable

HOwever, if I do the same thing on my development machine, adding a new portal alias and updating the HOSTS file to point to it, I can successfully see the site as WWW.MYCOMPANY.COM.

So I can't figure how why this isn't working to test the readiness of the site on the hosting server that is about to go live this week.

 I edited my HOSTS file to try to simulate the DNS change, repointing our existing public hostname to the new hosting IP to ensure that I don't have any missing / broken links, etc., prior to going live.

I have the site alias listed in the Site Settings. 

I'm wondering if this has to do with Host Header configuration settings on the hosting provider not having an entry for www.mycompany.com, but that's just a guess.

 

Any ideas? I don't want to go live without making sure that the site is ready to go without testing it first and using the entry in the HOSTS file to temporary change the IP address to point to the new webserver for that host name.

 

Any help would be appreciated because at this point, if I did make the DNS change to go live, everyone would get the "web page is unavailable". Not good at this point, but I"m sure it's probably something easy to deal with.

 
New Post
2/17/2015 2:37 PM
 
John,
a domain name in Hosts file points your request to the web server. Now IIS needs to know, which site to open, i.e. the IIS website needs a binding. The default site is usually bound to all addresses, however, in hosting scenarios, the provider will not enable default bindings.
Therefore you need to ask your hosting provider to bind WWW.MYCOMPANY.COM to your site as well (w/o name server entry).
The alias will tell DNN in a multisite install, which website to display (3rd step).

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/17/2015 3:17 PM
 

Danke, John. I can always count on you for some help.

 I contacted my hosting provider. They updated the host headers on their webhost that I"m on and it's now functional. I don't know why the main host header (www.mycompany.com) was missing, but it's set up now and I can conclude the pre-go live testing to make sure I don't have any issues.

Getting a little nervous about the launch. it's my first DNN site in quite a few years on a new web hosting company. I'm hoping the performance and issues are nothing too bad for now. Can always move later if I have to. I wish these hosting companies would be required to disclose how densely packed their webhosts are. But as long as I get reasonable performance for now, I'll be a happy camper!

 
New Post
2/17/2015 5:14 PM
 
I am glad I was able to assist.
Good luck for your go live !!!

Cheers from Germany,
Sebastian Leupold (Microsoft MVP)

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...portal alias testing/productionportal alias testing/production


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.

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  


Copyright 2017 by DNN Corp Terms of Use Privacy
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out