I am trying to configure a site binding on IIS10.
I want to be able to run multiple sites on the same ports and differentiate the sites by their host header.
For some reason IIS does not seem to resolve a host-name binding unless a specific interface is also selected.
I have previously configured sites on IIS 7.5 and 8.5 in a similar manner so I am at a bit of a loss to explain the behaviour I am seeing.
I have set up a new website with only a "hello world" html document to try an isolate my issue. The site is running on a port that is not used by any other website.
The host-name binding works, only if I also specify an interface.
Type | Host-name | IP address | Port | Works? |
---|---|---|---|---|
http | * | 30080 | Yes | |
http | host-troubleshooting.test.internal | * | 30080 | No |
http | host-troubleshooting.test.internal | 10.xxx.xxx.163 | 30080 | Yes |
In all cases I accessing the site using the same address and port: http://host-troubleshooting.test.internal:30080/
When I configure IIS to bind to the host and all IP addresses I get a generic 502 connection refused error
** Does Not Work **
Update
Using netstat it appears that there is nothing listening on the port when I have specified a wildcard ip address in the binding:
When a specific interface is selected; a listener is created