Tixy wrote: 
> 
> I can't see what the problem with DHCP is, if I want to have static IP
> addresses or use names to identify machines on the network, I can take
> a minute to add a line to dnsmasq.conf on my router. I know some people
> say that DHCP is a single point of failure, or they don't want to run
> extra hardware 24/7, but I would think most of us already have a router
> providing internet access that can do DHCP. And if that fails, have a
> spare (even if it's just an old device) that can be pressed into
> immediate use. I for one consider internet access sufficiently
> important to make fixing it a priority.

I use ISC dhcpd on two machines at home: my firewall and my
server. The failover system took about twenty minutes of reading
to figure out.

Then the firewall has unbound and the server has bind; unbound
does caching and general name resolution, and looks at bind for
my local names.

This is more complicated than it needs to be but I wanted to
experiment.

-dsr-

Reply via email to