From: Jonathan de Boyne Pollard on 20 Feb 2010 15:11 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> <meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type"> </head> <body bgcolor="#ffffff" text="#000000"> <blockquote cite="mid:E199C726-9D52-46EB-98BA-7C3B6619AA48(a)microsoft.com" type="cite"> <p>Are there issues with running IIS on machine with dynamically assigned IP address?</p> </blockquote> <p>Only the obvious ones that one would expect: </p> <ul> <li> <p>Locating the HTTP server by IP address will possibly involve changes in IP address, as different addresses are dynamically assigned.<br> </p> </li> <li> <p>Locating the HTTP server by a domain name will involve ensuring that the correct up-to-date name→address mapping is in the DNS database.</p> </li> <li> <p>The HTTP server will need to be configured to recognize the correct up-to-date IP addresses as host headers, or to ignore host headers.</p> </li> <li> <p>Firewalls and other ancillaries (including SSL certificates amongst other things) will need regular maintenance.</p> </li> </ul> <p>For public content HTTP service, getting this right is usually a lot of effort and involves service outages when information becomes stale. In particular this is because in the most common case the DHCP server, the content DNS server, and the content HTTP server are run by different people, and have no ties to one another. However, if one ties the three servers together properly, which involves back-channel communication amongst them, outages due to stale information can be avoided (or at least minimized, depending from how smart the content DNS server and DHCP server are). <br> </p> <p>On the gripping hand, statically allocated IP addresses bypass these problems and don't require such mechanisms, and hence are the preferred design. <a href="http://microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/f493ef15-df44-4493-83cd-20ccb2580c13.mspx">Microsoft's own recommendation is that dynamically allocated IP addresses and IIS do not mix</a>, largely for this reason.</p> </body> </html>
|
Pages: 1 Prev: IIS in windows 7 Next: Using outbound rules on sitemap.xml |