DotNetNuke Tips & Tricks

Tuesday, March 22, 2011 by Ian Robinson

Local virtual hosts with

Filed under: Tips & Tricks, DotNetNuke

Recently, Joe Brinkman posted a quick tip about using local virtual hosts for your DotNetNuke dev installs. The summary is that there are a couple of public domains out there that point to (which means they’ll hit your local IIS). These services Joe mentioned are and The benefit of using a service like this is that you can just assume your local domain will work and you don’t need to edit your machine’s hosts file.

So, after contemplating this for a moment, I thought it would be even better to set up such a domain specifically branded for DNN. So I registered and pointed it (and subdomains) to This allows you to set up as the binding in IIS instead of using http://localhost/yourprojectname or editing your hosts file to get

This may sound like just avoiding a trivial step, and in some respects it is, but I think it ends up making your dev environment just that much cleaner in the end. Here’s how I set things up for myself, just to give you an idea how you can use it.

Chrome browser screenshot shows URL of and the home page of a local DotNetNuke 6.0.0 CTP installation.

  • – the latest source version of DNN Community (5.6.1)
  • – the latest source version of DNN Community CTP (6.0.0)
  • – a copy of the website

In IIS on my local machine I have a few different web sites set up (as in right click Sites node and select “Add Web Site”). For consistency - I set each website name, host name (also known as binding) and its application pool name to be the same.



by Un paseo por las nubes
Wednesday, December 28, 2011 6:42 AM
blog comments powered by Disqus