glenn.satchell at uniq.com.au
Fri Apr 16 14:13:05 UTC 2010
And from the client's perspective it has released the lease. If that
client requests a new lease it will only get that IP back again. Even
though the server stores no state about the lease, the client can send a
request to renew the lease and the server will send an ack,
If you want the event and lease structure then perhaps using a reserved
lease would be a better option for you.
On 04/16/10 23:22, Darren wrote:
> It is indeed a host record with fixed-address statement. So there is no lease to release from the DHCP server's perspective. The client thinks there is, however, and seems to have no way to tell. Is this a wise design choice? I know it has been that way for a long time, but technically the address was "leased" from the client's perspective.
> On Apr 15, 2010, at 18:29 , David W. Hankins wrote:
>> On Thu, Apr 15, 2010 at 03:40:58PM -0400, Darren wrote:
>>> The difference I see here is that the release ended up on server-1 instead of server-2. It still wasn't "found", however.
>>> Since the release does not "find" the lease, no event is generated which is causing some problems in some other areas.
>>> Any idea what the deal is? Is this fixed in the 4.x.x tree?
>> Is this a host record with a fixed-address statement?
>> Host records have no state, and therefore no events.
>> David W. Hankins BIND 10 needs more DHCP voices.
>> Software Engineer There just aren't enough in our heads.
>> Internet Systems Consortium, Inc. http://bind10.isc.org/
More information about the dhcp-users