On Sat, 30 Dec 2017 23:34:52 +0000 (UTC)
Kiwi User  wrote:

> 3) Don't use DHCP at all: decide which is the master PC or RPi on your
>    LAN, ideally something that runs 24x7, and set up a DNS server on it
>    as the authoritative source for IP addresses for your LAN. Effectively
>    you give it the same information as goes into /etc/hosts if you use
>    solution (2) but now its only held in one place.
>
>    This probably has the steepest learning curve of the three, but
>    requires the least maintenance.
>
>    The most commonly used DNS servers are called 'bind' and 'unbound',
>    and are standard packages for almost all Linux versions, so
>    installation is dead simple: its just getting the moderately complex
>    configuration right that has the learning curve.

 For small networks there's dnsmasq which is much lighter and
simpler to manage than either bind or unbound (it uses hosts files not zone
files).

--
Steve O'Hara-Smith                          |   Directable Mirror Arrays
C:\>WIN                                     | A better way to focus the sun
The computer obeys and wins.                |    licences available see
You lose and Bill collects.                 |    http://www.sohara.org/

--- SoupGate-Win32 v1.05