Host Headers

Hi - I hoping someone can help me out. I've got a MS server 2003 running and I want to set up multiple web sites. Two of the sites are real domains. For the real domain sites, one I have set up as default with no header info and the other site I added my domain name for that site as the header info. All sites are using the same IP address.

When I point to the site with a header assigned I get the default site page. When I try and navigate to another page I cannot because it is confused. If I go directly to the default site, the site functions fine.

What am I missing Thanks for any suggestions!

Greg


Answer this question

Host Headers

  • V Williams

    Wow - this is so long ago that I forget what the resolution was (shame on me, I should have written it down). Here is what I think I remember.

    Site A is the default site without any header info. Site B is a separate web site on the same server with header info. These are the only 2 legal (internet) domains. Site B was configured with a header something like "SiteB.com". The server knew where site B was. The traffic coming in from the internet did not and delivered all of the traffic to (default) Site A. When trying to navigate off of the home page via the web site menu I got errors because the server thought is was on SiteB.com but it was really on Site A. If I was using this site in an intranet environment, I probably would not have this problem because my network DNS would take me to the server and the server would know where to go. The reason is that I would have put into my local DNS various names going back to the server. In the server I could have put various corresponding header values.

    The answer was to make the header value "www.SiteB.com" and not "SiteB". Then the internet packets came in with header info that the server understood.

    I didn't have another domain to create the problem for a Site C. If I used sub-domains, my best guess is that the I would have problems with all the sites that were not the default site. I think this was an ISP DNS issue. I needed to put into the header the exact same information the ISP had in DNS. My ISP did not put SIteB or SiteB.com into DNS. My ISP only had "www.SiteB.com" in DNS. Therefore I had to have the exact same "www.SiteB.com" in my header or internet traffic would just be delivered to the default web site..

    I hope this helps some.
    Greg


  • Derek0415

    Hi Greg,

    We apologize for not stepping in on this question earlier, but from the looks of it, you were able to resolve the issue and move forward.

    We'll let the engineer know how you resolved it. :-)

    cheers!
    -brenda (ISV Buddy Team)

    Need a Microsoft Buddy to help you navigate the jungle of information at Microsoft

  • wdcdba

    We passed your question on to one of our internal support engineers, who needs some clarification from you so that he can better understand the issue:

    In my understanding, your partner has two sites, one is the default site, for ex. site A, and another site B. Both site A and site B are hosted in IIS and site A doesn't have a HTTP head while B has. And the problem is that when your partner navigates to site B, the site B doesn't appear and site A appears. So my question is that, first, your partner mentioned that "
    When I try and navigate to another page I cannot because it is confused", would you ask him to give me a detailed instance for that kind of confusion I'm not clear with that. Second, what if we create a site C with head in this IIS, will site C also be redirected to the default site A Please do a test for me, thanks! And further, if we type http://siteb or http://sitec which page in site A will be displayed Please tell me so that I can look into it!
    < xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

    If you could post your responses here, I'll make sure that they get back to the engineer so that he can investigate this issue further.

    thanks!
    -brenda (ISV Buddy Team) 



  • Host Headers