I know I have asked this before but I cant seem to get it fixed and I have to get it done and I am running out of time. 

I have a DNN site that is on a server in house.  You can go to it via 12.27.134.116/dnn (the virtual directory) or simply typing in 12.27.134.116 (a redirection html file).  I didnt want to use the redirection file, however it was the only way I could get the DNN site to even run on the default web site instead HAVING to be a virtual directory. 

I want the site to be able to gotten to by using dev.hyper.com.  I did the following:
1)set a Host name with a pointer of dev in the DNS that points to the server (12.27.134.116) and allowed it to proprigate for 3 days.
2)inside the the DNN portal itself, set an alias of dev.hyper.com
3)inside the IIS (under the properties of the default web site which is the redirection), under website ident I used the IP address of 12.27.134.116 instead of (all unassigned) and then added the host header name of dev.hyper.com under andvanced.

After all this is done.  I get bad hostname or page can not be viewed.  Only after I take off the host header name and the IP address to (all unassigned) may I view the site again.  I need to get the IP address to resolve to dev.hyper.com soon.  Can anyone tell me what I missed???

Unfortunatelty here at the company, I became the IT person by default.  I never have done network until recently and have learned a ton.  I did it on ns1.hyper.com  Which is an inhouse one.  As far the one from atlantic.net (when I called them) they told me I have to do it on my local servers.  So, this is a matter for atlantic.net to help me with or was the person right and I have to do it on the local servers (which I am not sure if it will work for outside the network)?