<<
What would you put under custom header name and custom header value?
Is that what you're talking about? >>
No. Not
custom header,
host header. The host header is information sent with an HTTP request that contains the address the request is destined for and some other stuff. IIS can use the address in this header info to send the HTTP request to multiple virtual hosts on the same server IP address and port. So you can host hundreds of web sites using just one IP address.
In the IIS snap-in, if you look at the properties for your web site, on the web site tab, you'll see "Web Site Identification" and a description, IP address, TCP port, and an "Advanced" button. Click "Advanced" and then click "Add". Then choose the IP address to use for the site, the port to listen on, and then enter a host header name that is the same as the address of your site, for example,
www.mysite.com. You can do this for each site you want to host on the same IP address. And now each name will be directed to the right virtual site.
I have 11 sites hosted on my server using 1 IP. 3 are on the internet and 8 are local only for development. The 3 internet sites have fully qualified domain names in the host header field, and the names are resolved using standard DNS. The local sites just have single-word host header names (like site1, etc.) and the names are resolved using a hosts file on each client on my LAN. It works really well.