From: Jonathan de Boyne Pollard on
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<meta content="text/html; charset=ISO-8859-1"
<body bgcolor="#ffffff" text="#000000">
<p>Are there issues with running IIS on machine with dynamically
assigned IP address?</p>
<p>Only the obvious ones that one would expect: </p>
<p>Locating the HTTP server by IP address will possibly involve
changes in IP address, as different addresses are dynamically assigned.<br>
<p>Locating the HTTP server by a domain name will involve ensuring
that the correct up-to-date name&#8594;address mapping is in the DNS database.</p>
<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
<p>Firewalls and other ancillaries (including SSL certificates
amongst other things) will need regular maintenance.</p>
<p>For public content HTTP service, getting this right is usually a lot
of effort and involves service outages when information becomes stale.&nbsp;
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.&nbsp; 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).&nbsp; <br>
<p>On the gripping hand, statically allocated IP addresses bypass these
problems and don't require such mechanisms, and hence are the preferred
design.&nbsp; <a
own recommendation is that dynamically allocated IP addresses and IIS
do not mix</a>, largely for this reason.</p>