network admin, ip addresses for webserver

[Chris Green]

On Wed, Oct 29, 2014 at 04:10:34AM +0000, Thufir wrote:
> On Tue, 28 Oct 2014 22:54:05 +0000, Chris Green wrote:
> 
> > On Tue, Oct 28, 2014 at 07:58:00PM +0000, Colin Law wrote:
> >> On 28 October 2014 19:06, Patrick Asselman <iceblink at seti.nl> wrote:
> >> > On 2014-10-27 21:40, Colin Law wrote:
> >> >>
> >> >> On 27 October 2014 20:35, Thufir <hawat.thufir at gmail.com> wrote:
> >> >>>
> >> >>> Why is important for a server to use static ip address instead of
> >> >>> DHCP?
> >> >>> If it's behind a router, why not use that router's outward facing
> >> >>> IP address, and then the router will *route* to that hostname?
> >> >>
> >> >>
> >> >> Many (most?) routers require an IP address to be specified when
> >> >> setting up port forwarding, so the server needs a fixed ip address.
> >> >> Can your router take a host name instead?
> >> >>
> >> >>
> >> > My router allows one to set a preferred ip address for a particular
> >> > computer (or rather: mac address).
> >> > That way you can use port forwarding on the router as well as use
> >> > DHCP on the server.
> >> 
> >> Is that not just a different way of assigning a fixed ip address to the
> >> PC?
> >> 
> > Yes, but it means you don't have to reconfigure the PC to give itself a
> > static address.  You leave the PC configuration exactly as it was
> > picking up whatever the router gives it (plus the DNS, gateway and
> > default route), much simpler in many ways.
> 
> 
> To ballpark, what are the performance differences between allowing the PC 
> to use DHCP and have router assign a preferred ip address, versus an 
> actual static ip address?
> 
> This is for internal use only.
> 
I doubt it makes any measurable difference, once the systems 'know'
about each other (i.e. the DNS information is cached at each end)
I can't see why either static or dynamic would be faster. 

It will make a (very small) difference if you refer to a system by
name rather than IP address as there will be a DNS request to get the
IP but it's from a cache.

-- 
Chris Green