Ok, this is a weird one...there must be a setting some where that I am missing in the new version of DNN.

I just upgraded my development sites with 4.4.1.  If I hit the sites/portals from a separate machine, they get to the portals ok....but if I hit the sites/portals from the local machine (ie. http://localhost or http://servername or http://IPaddress) I can a DNS error...

ALL of the aliases are still there.  Since this is development, we have sites running off of ports, does the 4.4.1 version of DNN have problems with ports other than 80?  Like if I hit http://localhost:8080 it gives me the DNS error.

I have been developing on (before this week) version 4.3.4 with NO problems.

PLEASE HELP!  At a stand still.

Thanks!

Hi Ech,

Nope...I tried that...Gets DNS error.

ok, I got it....I didn't know this...My previous version was 4.3.4.

I guess in 4.3.6 a change was added so that now I have to add this to the "appSettings" area:
<add key="UsePortNumber" value="true" />

But that was not included in the "release.config" file for the 4.4.1 upgrade.

Note to DNN Core team, please add that to the web.config file :-)

thanks!