You can have as many aliases as you want for a portal, but I would get rid of ones you are not using anymore.

Another thing to note is that the very first alias is the one that DNN will redirect to if it gets a request that does not match any alias entry.

I can get my DNN portal to come up on the server's browser now using the Host file edit. THanks. I added the new alias names.

But I can browse to the new DNS name or to the IP address directly. But I can ping them.

I did get a message "Bad Request (Invalid Hostname)"

I am still working on it.

I can browse to the new name and DNN using the server's browser if I set the local Host file. But not if I use the new name. DNS is proagated correctly because I can ping the new name from my laptop.

Also, the webserver is working, because if I stop the DNN web and start a plain IIS web, I can browse a simple html home page from my laptop. If I start the DNN web instead, I get a page not found or a timeout.

I'm looking into IIS settings (though it worked fine with this server in the old location), and at the firewall settings in this new building.

Does DNN store or cache the old dummy.com name someplace?  I restated the entire server. In the portal alias on the Host menu/Portals settings page, I can add aliases, but I cannot edit or remove the original alias,