The information in this article applies to:
SUMMARY
This article describes how to use the HOSTS file to test a site that uses a host header name over an intranet. CAUTION: Modifying the HOSTS file on your computer incorrectly can interfere with name resolution. Be sure to make a backup copy of the HOSTS file before modifying it. After testing that the new site that uses a host header name is working properly, you may want to return your HOSTS file back to its original form.For information on how to use host header names on an IIS computer, please see the following Microsoft Knowledge Base article: Q190008 Using Host Header Names to Host Multiple Sites from 1 IP Address MORE INFORMATION
If the IIS computer that contains the site using the host header name is located on an intranet (a private LAN that uses Internet technology), that host header name must be first be registered with the intranet's name resolution system, such as the Windows Internet Name Service (WINS) before it can be browsed to. Add Entry for Host Header Name Site to HOSTS FileOn a local Windows NT computer, perform the following steps to update the HOSTS file, so that requests for the site using the host header name are routed to the correct IP address:
Test the HOSTS FileTo make sure the HOSTS file is working properly, go to a command prompt, and type PING HostHeaderName, where "HostHeaderName" is the host header name used by the new site.The reply should contain the same IP address that was returned earlier when Pinging the IIS computer. Browse the Site Using the Host Header NameIf the PING was successful, indicating that the intranet is routing connections to the host header name to the IIS computer, use a Web browser to load the new site, using the host header name.Additional query words: web ftp hostheader Domain Name Server DNS WINS
Keywords : |
Last Reviewed: August 16, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |