I can not access my web using www.domain.com. I get under construction error.
I can access it using ether http://domain.com or domain.com
I have host headers of http://domain.com, www.domain.com,
http://www.domain.com
I'm not sure what i should do?
On Oct 16, 5:44 pm, Dtsobel
> I can not access my web usingwww.domain.com. I get under construction error.
>
> I can access it using etherhttp://domain.comor domain.com
>
> I have host headers ofhttp://domain.com,www.domain.com,http://www.domain.com
>
> I'm not sure what i should do?
Host headers is half of what you need to configure. DNS is the other
half.
1. Users type in http://domain.com
2. Browser looks up domain.com in DNS to get an IP address
3. Browser makes request to that IP address
4. Server at that IP address routes request based on IP:Host:Port
binding (which includes domain.com as host headers)
You only configured #4. You need to also configure #2 so that browser
actually knows to go to your server for the Host headers to even
apply.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
I checked MY DNS records with my Domain register and they are fine.
There is something else going on.
I need help!
"David Wang" wrote:
> On Oct 16, 5:44 pm, Dtsobel
> > I can not access my web usingwww.domain.com. I get under construction error.
> >
> > I can access it using etherhttp://domain.comor domain.com
> >
> > I have host headers ofhttp://domain.com,www.domain.com,http://www.domain.com
> >
> > I'm not sure what i should do?
>
>
> Host headers is half of what you need to configure. DNS is the other
> half.
>
> 1. Users type in http://domain.com
> 2. Browser looks up domain.com in DNS to get an IP address
> 3. Browser makes request to that IP address
> 4. Server at that IP address routes request based on IP:Host:Port
> binding (which includes domain.com as host headers)
>
>
> You only configured #4. You need to also configure #2 so that browser
> actually knows to go to your server for the Host headers to even
> apply.
>
>
> //David
> http://w3-4u.blogspot.com
> http://blogs.msdn.com/David.Wang
> //
>
>
Please verify that request to www.domain.com actually comes to your
webserver, and if it arrives at your web server, that the request is
actually routed to the correct IIS website you defined. Check the IIS
log file for the request.
I believe the "under construction" web page is the default website
ID=1, in which case you currently see the www.domain.com requests
routed there. If that is the case, and you say you have configured
www.domain.com host header of another IIS website, then it means that
the DNS setting is incorrect and not causing the web browser to send
the www.domain.com host header.
If the web browser does not send the www.domain.com Host header after
DNS, then IIS will not route the request to your IIS website with
www.domain.com Host header.
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
On Oct 16, 8:54 pm, Dtsobel
> I checked MY DNS records with my Domain register and they are fine.
>
> There is something else going on.
>
> I need help!
>
>
>
> "David Wang" wrote:
> > On Oct 16, 5:44 pm, Dtsobel
> > > I can not access my web usingwww.domain.com. I get under construction error.
>
> > > I can access it using etherhttp://domain.comordomain.com
>
> > > I have host headers ofhttp://domain.com,www.domain.com,http://www.domain.com
>
> > > I'm not sure what i should do?
>
> > Host headers is half of what you need to configure. DNS is the other
> > half.
>
> > 1. Users type inhttp://domain.com
> > 2. Browser looks up domain.com in DNS to get an IP address
> > 3. Browser makes request to that IP address
> > 4. Server at that IP address routes request based on IP:Host:Port
> > binding (which includes domain.com as host headers)
>
> > You only configured #4. You need to also configure #2 so that browser
> > actually knows to go to your server for the Host headers to even
> > apply.
>
> > //David
> >http://w3-4u.blogspot.com
> >http://blogs.msdn.com/David.Wang
> > //- Hide quoted text -
>
> - Show quoted text -