dotnetnuke configuration error

domain name "[domainname]" does not exist in the database

dotnetnuke supports multiple portals from a single database/codebase. it accomplishes this by converting the url of the client browser request to a valid portalid in the portals database table. the following steps describe the process:

1. web server processing
  • when a web server receives a request from a client browser, it compares the file name extension on the target url resource to its application extension mappings defined in iis.
  • based on the corresponding match, iis then sends the request to the defined executable path ( aspnet_asapi.dll in the case of requests ).
  • the aspnet_isapi.dll engine processes the request in an ordered series of events beginning with application_beginrequest.

  • 2. application_beginrequest ( globals.asax.vb )
  • the request url is parsed based on the "/" character
  • a domain name is constructed using each of the relevant parsed url segments.


    url: = domain name:
    url: = domain name:
    url: http://localhost/dotnetnuke/default.aspx = domain name: localhost/dotnetnuke
    url: = domain name:
    url: = domain name:

  • using the domain name, the application queries the database ( portals table - portalalias field ) to locate a matching record.

    note: if there are multiple urls which correspond to the same portal then the portalalias field must contain each valid domain name in a comma seperated list.


    url: http://localhost/dotnetnuke/default.aspx
    url: http://machinename/dotnetnuke/default.aspx
    portalalias: localhost/dotnetnuke,machinename/dotnetnuke,

    note: if you are installing the application to a remote server you must modify the portalalias field value for the default record in the portals table according to the rules defined above.
  • louis vuitton outlet