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!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Using IIS Admin.Net with DNN

The one limitation I hate with XP Pro is that you can only have 1 web sites.
For DNN what this means is that all you DNN sites have to run under a Virtual Directory and there was no easy way to configure DNN to run as a Site instead of a virtual directory. In the early days this could be overcome by using some of the IIS Admin scripts to create additional web sites, but it was not for the faint-hearted.  Another way to overcome this was just to update the default web site to the DNN site you wanted to work on. Then along came IIS Admin / IIS Admin.Net and overcoming this issue became a whole lot easier.  Below is step-by-step instructions on how to user IIS Admin.Net

Scenerio: You have 2 web sites: and  You want to use the URL's above on your local machine, so you can mimic what they will be in production.

1) Download and install IIS Admin.Net.  You can download it here.
2) Install DNN for the first site you need to create.  DO NOT access the web site during this step, just install the files, update the web.config, etc.  You will finish the install afer you have created the site using IIS Admin.Net.

3) Open IIS Admin.Net and click the [Create] button.

4) Enter the information for the new site.  Do not put any spaces in the description. Although it allows it this can cause other problems.  I also like to have my description be the same as the domain (,, etc)

  • DNN3: Home directory should be the directory DNN was installed into, C:\IneptPub\wwwrroot\mySite1Dev.
  • DNN4: The Home directory should be the website directory that is under the directory that DNN was installed into, C:\IneptPub\wwwrroot\mySite1Dev\WebSite.
5) Click the [Open IIS] button.

  • Highlight the web site just created, right click and choose properties.
  • On the web site tab, click the [Advanced] button.
  • Highlightt the single entry (port 80) and click the [Edit] button.
  • Enter as the host header.
  • Apply changes and exit IIS Manager.
  • The first time settng up IIS Admin.Net follow the same instructions   above for the default site and set the host header to localhost.  This will stop the other domains you setup from accidently running under the default web site.
6) Edit the hosts file (C:\WINDOWS\system32\drivers\etc\hosts) and add entries the new site you just created.  Make sure you save the changes.

    #DotNetNuke Local URL's

7) Verify host file changes have been saved by going to a command prompt and pinging the site domain (ping and it should response back on IP

8) Double click on the site you just created to start that site (

9) Access the site now using the new domain (

10) If you are using the source code version of DNN you have one final step, and that is to update the solution file so each DNN solution points to the new URL (, etc)

  • DNN3: There are multiple solution files and they are all stored in the solution directory under the root.
  • DNN4:  The solution file is stored in the root installation directory.
11) Repeat steps 3-10 for each sites you want to setup.

You can now access each of your DNN installations using the new domains you have registed in your hosts file (,, etc).  All you have to do is go into IIS Admin.Net and double click on whatever site you want to access, to start up the site in IIS.  One you start using IIS Admin.Net, it will become one of the tools you cannot live without.

Note: You can also setup each site to run as a virtual directory while at the same time also be able to run it as a web site.  below is the additional  steps on how to do this.

1) Create a virtual direcotory that points to the same home directory as the sites above.

  • DNN3: Home directory should be the directory DNN was installed into, C:\IneptPub\wwwrroot\mySite1Dev.
  • DNN4: The Home directory should be the website directory that is under the directory that DNN was installed into, C:\IneptPub\wwwrroot\mySite1Dev\WebSite.
2) Acces the sites using the web site URL and add the alias for the localhost (localhost\{mysite1Dev}).

Now when the default web site is running you can use http://localhost/mysite1Dev and when the is running you can use

I hope this information makes development life easier and I will appreciate any feedback given.


Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out