In article <199902081858.NAA03684@grosse.fugue.com> mellon@hoffman.vix.com (Ted Lemon) writes:
>
>So I just hacked an authoritative flag.   For dhcp 2.0, the default
>will be that you are authoritative, because I don't want to change the
>default at this late date - it'll break more configurations than it
>fixes.   In 3.0, the default will be not authoritative.   The
>declaration looks like this:
>
>subnet 10.2.3.0 netmask 255.255.255.0 {
>       not authoritative;
>       range 10.2.3.10 10.2.3.15;
>}
>
>I'm in the middle of a 2.0 release process.   When that's complete,
>I'll import the new code - definitely before 1.4 freezes.   If you
>want to see it sooner, I'm preparing a new test release, 2.0b1pl11,
>which will be in ftp://ftp.isc.org/isc/dhcp/test sometime later on
>today (soon).

I think that you want to make the default not authoritative right now.
I ran into a big problem trying to make NT's dhcp server coexist with
NetBSD's dhcpd.

christos