It seems like there should be an obvious solution to this that I'm simply missing...

I have DNN set up and running correctly as a virtual directory under the default website in IIS. Platform is Server 2003.

I expect to be hosting a number of sites on this installation, and the behavior I am trying to get is where each domain resolves properly to the DNN application which in turn resolves the domain to a portal alias. I am trying to accomplish this so that the URL is *not* [somedomain]/dnn (where /dnn is the virtual directory where the app lives).

The most elegant solution I've come up with is where the default website under IIS adds "/dnn" to the url of the incoming request. This is using the IIS default website properties "website is a url" option and "add directory to url" suboption. This way, I don't even need to register each domain within IIS, just as portal aliases in DNN. The default website picks up any incoming domains that aren't assigned to other websites, adds "/dnn" to the request which resolves it to DNN, and DNN in turn resolves somedomain/dnn to a portal alias. The downside is that every single URL has that additional directory added to it. Maybe I'm picking nits, but this bugs me.

So, is there a way in IIS to resolve incoming domains to a DNN installation without adding a subdirectory? Thanks.

this was the first thing I tried. I get a 404 when I try this method, and assumed it had to do with dnn needing to run as either a virtual directory or application, like on my vista dev machine. Yes, the value is in the portal alias list. I wonder if it is the version of IIS that I'm running? It is whatever came on a 2003 install. Help | about doesn't give me a version, just some mmc information.

Still no joy. Well, off to the UK for 5 days. I'll mess with it when I get back. Thanks for the suggestions so far.