I've been getting all sorts of odd behaviour since starting to use Child Portals.  DNN seems to get 'mixed up' between aliases, with some going to a parent portal (same domain) when the child portal alias is there.

I've removed the parent portal completely for the same domain but I now have a child portal alias for a separate domain which certainly exists, getting redirected to the first/main parent portal for the DNN instance.

For example...

http://www.differentdomain.com/ABCenterprises  (child portal alias) is always redirecting to http://www.ABCenterprises.com (main/first parent portal)

http://www.differentdomain.com/ABCenterprises/Home/tabid/2908/Default.aspx  but this isn't redirected and works!

Why would this be happening at all?

Thanks Alex for the reply.

I found out why this is happening, which is related to my earlier post where there's a problem with updating things (including adding portal aliases) from one DNN portal (same instance) for another which is accessed via a different IP address for SSL reasons.

I keep needing to recycle the app pool to get the changes reflected, which I hadn't done so the Child Portal here (different IP address, same DNN instance) wasn't picking up on the aliases and diverting to the main/first portal.

Is this something to do with the cache?  Or possibly a better way to set this up in IIS , or settings to use for the App Pools?

Thanks

I can answer this one for you : yes, it is to do with the cache.  However, it's not the module cache, it's the DNN level cache which you can't switch off.  When you restart your application (you can do this via the host settings page, instead of IIS or the app pool) the portal alias cache gets rebuilt.  If you ever change the portal alias table directly, it's always important to rebuild the cache via restarting the application.