1

I am wondering when I am creating a new website should I choose an ip address from the list or leave it "unassigned ip address"?

Thanks

0

Typically you would leave it unassigned unless any of the following (as examples):

1) You have multiple SSL Sites that do not support SNI (like vhosts for SSL), so you must map an SSL and IP to the site's FQDN.

2) You have multiple networks interfaces and do not want to listen on all interfaces and all IPs.

3) Your site is behind a local proxy, and you want to prevent bypassing the load balancer (also recommend non-standard ports if doing this method or dedicated load balancer), common for tomcat or nodejs.

  • One of my sites is going to get SSL the rest won't. I am planning to have multiple sites hosted in my iis currently I have 2 hosted with "unassigned" with no problems right now though I have not done the SSL one yet. Will I run into any problems? – chobo2 Oct 29 '16 at 19:59
  • it's only an issue if you have multiple SSL sites and don't support SNI, (2012 R2 should have a check box to enable SNI) – Jacob Evans Oct 29 '16 at 20:55
  • if your audience uses modern technology, expect to use SNI and ssl all sites, http2 required ssl, I assume you'll want to support that soon. – Jacob Evans Oct 29 '16 at 21:02
0

Depends on what you are going to do in the future. If you are only ever going to have one thing running on IIS, it shouldn't matter. If you start hosting multiple sites, you will need to assign an IP address to each one. See here for further information: https://technet.microsoft.com/en-us/library/cc753195%28v=ws.10%29.aspx?f=255&MSPPError=-2147217396

Thanks, Tim.

  • I have already hosted 2 websites(both add website) both with unassigned and have not run into a problem with the IP. – chobo2 Oct 29 '16 at 20:00
0

It really depends on your plan in the future and the version of IIS you're using. There will be different strategies based on which IIS version you are using.

If you're using IIS 7.5 or less and you install an SSL Cert - You can only assign one SSL per IP. So you will need different IP's for each site you want SSL Certificate on. Remember the Site and the SSL Cert must match.

Now with IIS 8.0 that limitation is lifted with the SNI Feature.

So with host headers, you're not going to run into an issue with "unassigned" IP's, but once you add in SSL and depending on which version of IIS you are using, you're going to have some decisions to make.

  • I am using I think ii8(windows-server-2012) so it sounds like I won't have to worry about this when I do my ssl sert? – chobo2 Oct 29 '16 at 20:23
  • yeah, with IIS8 and the right settings checked you'll be ok. – Henry Oct 30 '16 at 0:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.