If I set up a website in IIS with a hostname (local.somewebsite.com) (having added it to HOSTS file) and also specify an IP address (127.0.0.1), the website is accessible by the hostname, but hitting it by the IP seems to load the default website and gives a not found message.
Is this expected behaviour? The workaround seems to be pointing the default website back to the folder of the website.
The reason for this question is that we've got a number of websites in a server farm, and one particular action is meant to call the other servers and clear the cache on each of those, so the websites are accessed by both hostname and by IP.