What does 'All Unassigned' actually mean in IIS IP address allocation? 1

[Skittle]

When adding a website or FTP site, you can specify a specific IP address.

The default is 'All unassigned'.
I expected this to mean all IP addresses not specifically assignd to another web site or ftp site on my IIS server.
In fact it seems to mean 'all IP addresses on server'
regardless of wether or not the Ip address is used for another IIS site.

Am I missing something? Does 'All unassigned' mean 'all'?



Dazed and confused

 

[safaritek]

All undefined means both of your thoughts.

For example, you have the following IPs on the server

66.111.111.22
66.111.111.23
66.111.111.24

You have the following sites on the server

http://www.site1.com

= 66.111.111.22

http://www.site2.com

= 66.111.111.23

http://www.site3.com

= all undefined

http://www.site4.com

= 66.111.111.22

(yes, as long as you use domain headers you can assign more than 1 site per IP)

In the above scenario, if you enter:

127.0.0.1 or localhost or 66.111.111.24 or ww3.site1.com (as long as there is a DNS going to your server), they will all end up on

http://www.site3.com

because they are defined in your headers and IPs

The server looks at both the IP and the header assigned it it ... if there are no exact matches, it will go to the site marked as "all undefined".

By default, it looks at the IP if no header is defined. If there IS a header defined, and you want the IP to also work (i.e. 66.111.111.22 and

http://www.site1.com

to both go to site 1) then you have to add the IP address to the header as well .... otherwise the IP will also end up at the undefined site.

In Summary, if there is no exact match in the headers for the site, then it goes to the default site as a catchall.

 

[Skittle]

Simply excellent answer.
Thanks.

Dazed and confused