Dorkian,

You might have a different problem.  Your domain is pointing to an IP in Dallas, TX but you are registered in La Brea, CA and the DNS servers are parking servers at Godaddy.  The only IP associated with the domain is 69.93.0.166 which might be a mail server.  If that is the IP of your connection to the internet you should be fine with the set up I think you have.  If not then you will need to use the control panel at godaddy to update your DNS records.  (Only do that if you really know what you are doing.)  The change might take from 1 hour to three days to get to you depending on the DNS servers between you and everything else.

localhost/DotNetNuke is a good idea to have in there if your DNN install is in a virtual directory named DotNetNuke.

Cheers,

---

Paul Davis

ahrensy,

Exactly.  I was just trying to figure out how he has IIS and DNN configured.  Your post is spot on how it's supposed to work.  I wouldn't put an IP in the portalalias either for just that reason.

---

Paul Davis

I'm just guessing here but I doubt that DNN will work in that configuration without being in a virtual directory under webroot.  Because DNN is really trying to do the same things as the host headers are doing. 

I'm going to leave it here and hope that maybe someone from the DNN team can answer this or possibly one of the guys that runs a host provider out there.  There is a guy posting around here called MrMobileNow that might have an idea for you.  I'm pretty sure he has something to do with powerDNN.

---

Paul Davis