I am a novice with DNN, so please bear with me. Thanks.

I've had my small site running just fine on a machine on my home office network. Before pointing the real url www.designet.com to this new site, I've been using the hostname www1.designet.com for testing.

Until this morning, I was able to get to the site ok from the host machine itself using the localhost url, from other machines on the internal netowrk using the host machine [192.168.1.18] IP address or the www1.designet.com name, and from entirely outside the firewall. Suddenly, this morning, I can only get to the site from the host machine itself. Can't get to it from any other machine inside or outside the firewall using any url construction - host name or straight IP address. When I am on the host machine, I can navigate the whole site with no problems using the localhost/... addresses. The site doesn't respond to the www1... address even on the local machine. I think I broke something - not sure what.

I can ping the host machine just fine inside the network. Public DNS seems to be working fine for www1.designet.com. I can Remote Desktop into it via the IP address from inside the firewall. I tried starting and stopping IIS. I rebooted the server. I set the firewall so that the DNN server is fully exposed as a DMZ. None of this helped. For some reason, IIS or DNN won't respond to anything but localhost/.

I have two HTTP Alias' setup, but I changed the order to try to fix the problem. Should they be in a particular order? Right now, the localhost alias is at the top of the list.

Is there anything in the web.config file that could be causing this problem. I saw I had an open copy of it at one point, and just closed it.

If anyone could give me some troubleshooting guidance, I would greatly appreciate the help. Thanks.

Jim

Thanks Sebastian. I made that change yesterday. The external address is now first in the list.

I also made a change related to the internal IP address that the machine is using. I have two subnets running over the same physical network. The 192.168.0.XXX network is my private network. The 192.168.1.XXX network is a DMZ, and accessible from the internet. I had assigned the dotnetnuke system an IP address on both subnets so it would be easily accessible from both inside and outside. Thinking there might be some kind of IP conflict, I removed the inside address.

The combination of the alias and the IP address change seems to have provided access and stability - at least for now. Thanks for your help, Sebastian.

Jim