IIS can be reached by IP only

Your DNS server is failing to resolve the name "server1" into an IP
address. If you know you have a DNS server properly configured to
resolve your url, then look for another "rogue" DNS server that maybe
running local to your client that is intercepting the HTTP request and
attempting to do the resolution instead.

Another problem that can occur is that all DNS servers buffer the
resolution of a URL so that they don't have to look it up again on
subsequent calls. The "A" record used for your url in DNS also
specifies the period of time that DNS caches the resolution. If you
have continually had unsuccessful resolutions on a particular DNS
server, that server may have "learned" that the url doesn't exist and
is reporting this from its cache rather than actually looking it up.
The solution to this is to have shorter expiration times on your DNS
records.

Andy
 >> Stay informed about: IIS can be reached by IP only 

I'm fairly new to IIS. Does it log only to the Event Viewer ?

What do you mean by bindings ?
If you mean IP address bindings, I can ping the server on each of the ip
addresses. In fact the virtual server which is playing up can be telneted
to on port 80. It does reply.


Cheers,









Hello Kristofer,

> What do you mean by "it cannot be reached"? What do you observe? Any
> error messages?
>
> Do you perhaps use DotNetNuke? For what i know, it has a setting that
> maps to the host header so that may be wrong.
>
> It can also be a setting in IIS. Check the bindings for the website,
> what does it say?
>
> "RogerDodger Administrator" <roger.RemoveThis@mail.com> skrev i meddelandet
> news:7d7bba6b06d38ca44372c11266c@msnews.microsoft.com...
>
>> We are running IIS 6, with multiple virtual folders eacher with own
>> IP.
>>
>> We can reach the web server from IP
>> http://10.0.0.1/DotNetNukum
>> However when we try and reach it with http://server1/DotNetNukum it
>> cannot be reached.
>>
>> I have used nslookup and can resolve the IP to hostname, and vice
>> versa. The ip address and hostname is accurate mapping.
>>
>> This is driving me nuts. Can it be IIS, or has anyone else
>> experienced this and can provide me with some tips ?
>>
>> thank you
>>
 >> Stay informed about: IIS can be reached by IP only 

No, it logs to several places, the IIS log file, the httperr file are two
other places.

But i still need to know what you observe. What do you see in your browser?

For the bindings:
In IIS Manager, right click the website and click Properties.
Click the Advanced button.

What are the bindings?

--
Regards,
Kristofer Gafvert
http://www.gafvert.info/iis/ - IIS Related Info


"RogerDodger Administrator" <roger RemoveThis @mail.com> skrev i meddelandet
news:7d7bba6b12348ca46f5db2ed5ac@msnews.microsoft.com...
> I'm fairly new to IIS. Does it log only to the Event Viewer ?
>
> What do you mean by bindings ?
> If you mean IP address bindings, I can ping the server on each of the ip
> addresses. In fact the virtual server which is playing up can be telneted
> to on port 80. It does reply.
>
>
> Cheers,
>
>
>
>
>
>
>
>
>
> Hello Kristofer,
>
>> What do you mean by "it cannot be reached"? What do you observe? Any
>> error messages?
>>
>> Do you perhaps use DotNetNuke? For what i know, it has a setting that
>> maps to the host header so that may be wrong.
>>
>> It can also be a setting in IIS. Check the bindings for the website,
>> what does it say?
>>
>> "RogerDodger Administrator" <roger RemoveThis @mail.com> skrev i meddelandet
>> news:7d7bba6b06d38ca44372c11266c@msnews.microsoft.com...
>>
>>> We are running IIS 6, with multiple virtual folders eacher with own
>>> IP.
>>>
>>> We can reach the web server from IP
>>> http://10.0.0.1/DotNetNukum
>>> However when we try and reach it with http://server1/DotNetNukum it
>>> cannot be reached.
>>>
>>> I have used nslookup and can resolve the IP to hostname, and vice
>>> versa. The ip address and hostname is accurate mapping.
>>>
>>> This is driving me nuts. Can it be IIS, or has anyone else
>>> experienced this and can provide me with some tips ?
>>>
>>> thank you
>>>
>
>
 >> Stay informed about: IIS can be reached by IP only 

RogerDodger Administrator avait énoncé :
> We are running IIS 6, with multiple virtual folders eacher with own IP.
>
> We can reach the web server from IP
> http://10.0.0.1/DotNetNukum
>
> However when we try and reach it with http://server1/DotNetNukum it cannot be
> reached.
>
> I have used nslookup and can resolve the IP to hostname, and vice versa. The
> ip address and hostname is accurate mapping.

I have experienced this few weeks ago, but found no solution. It is not
a DNS problem too because name resolution maps to the correct IP.

Did you find a solution ?

Best Regards.

--
Stef
 >> Stay informed about: IIS can be reached by IP only