From owner-freebsd-questions@FreeBSD.ORG Thu Jan 1 14:10:23 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1835916A4CE for ; Thu, 1 Jan 2004 14:10:23 -0800 (PST) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id A1C1643D2F for ; Thu, 1 Jan 2004 14:10:21 -0800 (PST) (envelope-from tillman@seekingfire.com) Received: by mail.seekingfire.com (Postfix, from userid 500) id 89A5B11F; Thu, 1 Jan 2004 16:10:20 -0600 (CST) Date: Thu, 1 Jan 2004 16:10:20 -0600 From: Tillman Hodgson To: Free BSD Questions list Message-ID: <20040101221020.GR99973@seekingfire.com> References: <20040101220623.GC7730@teddy.fas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040101220623.GC7730@teddy.fas.com> X-Habeas-SWE-1: winter into spring X-Habeas-SWE-2: brightly anticipated X-Habeas-SWE-3: like Habeas SWE (tm) X-Habeas-SWE-4: Copyright 2002 Habeas (tm) X-Habeas-SWE-5: Sender Warranted Email (SWE) (tm). The sender of this X-Habeas-SWE-6: email in exchange for a license for this Habeas X-Habeas-SWE-7: warrant mark warrants that this is a Habeas Compliant X-Habeas-SWE-8: Message (HCM) and not spam. Please report use of this X-Habeas-SWE-9: mark in spam to . X-GPG-Key-ID: 828AFC7B X-GPG-Fingerprint: 5584 14BA C9EB 1524 0E68 F543 0F0A 7FBC 828A FC7B X-GPG-Key: http://www.seekingfire.com/gpg_key.asc X-Urban-Legend: There is lots of hidden information in headers User-Agent: Mutt/1.5.5.1i Subject: Re: using multiple isc-dhcp servers? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2004 22:10:23 -0000 On Thu, Jan 01, 2004 at 05:06:23PM -0500, stan wrote: > 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. > > This seems like a problem. Yes, I imagine it is ;-) > How can I configure this package to avoid this problem? You shouldn't have more than one DHCP server per broadcast domain (unless you implement some sort of database sharing logic between them). Because clients keep their leases for a period of time even if the DHCP server dies, this isn't a service that typically calls for redundancy. -T -- "Nostalgia is a seductive liar." - George W. Ball