I have the community version and pro trial of DNN 5.x.x installed on a windows 2003 server. I'm trying to use host headers with DNN and one host header works but the other does not.

example:

In IIS I have two host headers entered:
server ip (x.x.x.240), port 80, dnncomm
server ip (x.x.x.240), port 80, dnncomm.xyz.org

In DNN Alias listing I have three:
server ip (x.x.x.240)
dnncomm
dnncomm.xyz.org

In the web.config file I have:
<add key="HostHeader" value="dnncomm.xyz.org" />

In DNS I believe my network guy just entered dnncomm.xyz.org as an A record pointing it to (x.x.x.240)

So when I type in dnncomm into my address bar the site appears to work just fine, but when I type in dnncomm.xyz.org I get the following message:

Bad Request (Invalid Hostname)

Any ideas?

Sorry, I wasn't clear enough in my previous post. I have three websites. Two DNN sites (one is the community 5.x version and the other is the professional 5.x version) and one html static site. So yes I do need to specify different host headers, because we are using the same IP to back all three sites. At the command prompt I can ping both dnncomm and dnncomm.xyz.org and i get successful replies back from both pointing to x.x.x.240. I've listed more details below for more info. Being that I can ping all four (dnncomm, dnncomm.xyz.org, dnnpro, dnnpro.xyz.org) names with successful replies, my network guy says DNS appears to be working fine. Does this issue have to do with the DNN alias's that are in each DNN config? We are new to host headers and that is where our network team wants to go with down the road instead of assigning a new IP address to every new website on the server.

Community 5.x version
IIS host header setup: (I only used one header this time)
server ip (x.x.x.240), port 80, dnncomm

In DNN Alias listing I have three:
server ip (x.x.x.240)
dnncomm
dnncomm.xyz.org

In the web.config file I have:
<add key="HostHeader" value="dnncomm.xyz.org" />

Professional 5.x version
IIS host header setup: (I only used one header this time)
server ip (x.x.x.240), port 80, dnnpro

In DNN Alias listing I have three:
server ip (x.x.x.240)
dnnpro
dnnpro.xyz.org

In the web.config file I have:
<add key="HostHeader" value="dnnpro.xyz.org" />

TIA...

 

Hey DNN.  Why all the silence and ambivolence about Host Header functionality?  From a quick google search Fred and many other DNN Admin/users have the same, unanswered question.    How can DNN mimic IIS' Host Header functionality so as to host multiple DNN sites using a single IP address?  To be clear, the goal is to have www.myDomainName.com resolve to one DNN site and www.yourDomainName.net resolve to a different DNN site hosted by the same DNN instance.

If it is already built in to the Community Edition 5x, it's very poorly documented.
Please explain.