all domains have to be bound to the same IIS web site and get directed to dotnetnuke default web site. the core framework analyses the requested url and looks for the appropriate portal assigned to the domain address via a portal alias. next, page ID gets derived from rest of the path as well as other required parameters. HTH

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

To try to make this a little simpler...

The first thing to remember is that a combination of your website hosting company and your domain registrar need to help you get a url (website address) to point to your physical website.  If your hosting company and your domain registrar are the same company, this is much easier.  But in any event, once a website address is pointed at your DNN site, DNN handles it from there.

DotNetNuke has the notion of multiple "portals" or "sites".  And any site can answer to requests for one or more urls.  In DNN parlance, these different urls are referred to as Portal Aliases.  If you are logged into your site as a Host user and navigate to the Site Settings (or via the Host menu, you can manage Portals), you'll find a list under Advanced Settings for managing the list of portal aliases. 

When your DNN site receives a request through the webserver (IIS)... it looks at the request, see's the url and identifies in the database which site is actually being addressed.  That tells it which set of data to serve up.  But configured in this way, any number of sites and url's can by used by a single DotNetNuke instance.

---

Scott Willhite, Co-Founder DNN