DotNetNuke 5.06.01 is expected to be released around the middle of next week - January 19th according to Joe Brinkman's recent blog post. A 5.06.01 Release Candidate was posted to the CodePlex downloads site yesterday: http://dotnetnuke.codeplex.com/releas....

If you are able to test the RC on a clone of your 5.06.00 site (not on the production server unless you are 100% certain that you have good backups of both filesystem and database and are willing to roll back if necessary), that would be helpful to others experiencing the same or variations on the URLRewriteModule/automatic-portal alias mapping issues.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner

I've been having the same problem. However, I didn't notice the issue with the default (host) portal at first. (dnn.mysite.com/portal1) It was only apparent when adding a new portal then trying to access it at dnn.mysite.com/anewportal. As a new user I thought I was doing something wrong and must have re-installed half a dozen times in the last couple of days.

It was only when loading up dnn.mysite.com/portal1 this morning and getting the error page that I dug deeper. Yes, adding "default.aspx" to the URL made the page load but the default document, as set in IIS, was not loading when opening the site. The answer is that this is a bug and it is fixed by 5.06.01. Having installed the 5.06.01RC update (rather than yet another new install!) the site now works fine. Although I agree with Chris that this was a big miss by QA, at least it's sorted now. I trust the final release version will be rolled out ASAP.