Date: 01 Jan 2004 19:55:41 -0500 From: Lowell Gilbert <freebsd-questions-local@be-well.ilk.org> To: stan <stanb@panix.com> Cc: Free BSD Questions list <freebsd-questions@freebsd.org> Subject: Re: using multiple isc-dhcp servers? Message-ID: <443cazw4mq.fsf@be-well.ilk.org> In-Reply-To: <20040101220623.GC7730@teddy.fas.com> References: <20040101220623.GC7730@teddy.fas.com>
next in thread | previous in thread | raw e-mail | index | archive | help
stan <stanb@panix.com> writes: > I have set up the isc-dhcp port on 2 machines. and it is serving addresses, > but I notice that whichever machine gives the lease is the only one that > records the lease in it's leases file. Right. If you want them to know about each other, you need to configure that. See the descriptions of "failover" in the dhcpd.conf(5) manual. > This seems like a problem. Not unless both servers are serving addresses out of the same pool. Obviously, that *would* be a problem. If one hands out (for example) 10.0.0.3 through 10.0.0.127 and the other hands out 10.0.0.128 through 10.0.0.254, then there's no problem at all. You can have the second one respond more slowly by using the min-secs statement in its configuration. > How can I configure this package to avoid this problem? If you want the failover support, then you can set that up (I've never done it, but it looks reasonably simple when I read the manual). It's probably not worth setting up two servers, though. If you have a reasonable gap between the renew time (when the clients start looking for a new lease) and the end of the lease (when the clients have to stop using their old lease), then you have a fair amount of breathing time to get the server fixed. -- Lowell Gilbert, embedded/networking software engineer, Boston area: resume/CV at http://be-well.ilk.org:8088/~lowell/resume/ username/password "public"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?443cazw4mq.fsf>