Nope, that didn't work.
In your opinion does my script to redirect Albigen.Net to the DNN directory conform with standard procedure in a case where the hosting provider will not point a domain name to a subdirectory?
I'm starting to wonder whether my hosting provider is somehow caching the SQL data, but that's a different issue.
I need to reserve Albigen.Com as the root because I have other applications above it, only one of which is DNN, which is in the /portals subdirectory. But to make sure, I tried your suggestion anyway.
Since I'm in the process of upgrading DNN - I'll probably end up editing the portal aliases on my local server, wiping out the current installation and database on the website, and pretend like I'm starting over from scratch. Obviously the website alias can't be edited from the website while the application is running, but I can edit the website alias when the application is running on my local server.
One distracting idea is the notion that the only differenxce between a child portal and a parent portal is that the child portal has a subdirectory. But that's only a side issue, because the HomeDirectory field in the Portals table is indicated to be Portals/0, which is as it should be.
I don't see a field anywhere in the database that designates whether the portal is a parent or a child, so maybe this is simply implicit - i.e., a reflection of the portal alias URL.
Anyway, thanks again, appreciate your help. Steve