IIS does not automatically do reverse DNS lookups - by default, Request.ServerVariables("REMOTE_HOST") is populated with the same value as Request.ServerVariables("REMOTE_ADDR") - which is simply an IP address. According to
KB #245574 and
KB #297795, you can configure IIS to handle DNS lookups. Barring that ability, here are some components that will facilitate it without altering IIS:
AspDNS ASPDNS BrowserHawk DNS LookUp DSDNS DynuDNS HexDNS LyfDNS Simple DNS+Traceroute Remember that reverse DNS lookups on every request can be a significant burden on your server... so only implement one of these solutions if you really need it! Also remember that performing a reverse DNS lookup doesn't necessarily give you accurate results. Statistics Server, for example, returns the state that AT & T's regional office is in, not the state where they provide our bandwidth.