DHCP losing client lease

[tgagne]

I have a Suse 10.3 laptop with the hostid tgagne2. When it boots up its leases an IP address without a problem but a few minutes later it loses it.

Here's the original request:

Mar 30 06:45:09 localhost named[20324]: client 127.0.0.1#34845: signer "ddnskey" approved
Mar 30 06:45:09 localhost named[20324]: client 127.0.0.1#34845: updating zone 'home.lan/IN': adding an RR at 'tgagne2.home.lan' A
Mar 30 06:45:09 localhost named[20324]: client 127.0.0.1#34845: updating zone 'home.lan/IN': adding an RR at 'tgagne2.home.lan' TXT
Mar 30 06:45:09 localhost dhcpd: Added new forward map from tgagne2.home.lan to 192.168.1.222
Mar 30 06:45:09 localhost named[20324]: client 127.0.0.1#46006: signer "ddnskey" approved
Mar 30 06:45:09 localhost named[20324]: client 127.0.0.1#46006: updating zone '1.168.192.in-addr.arpa/IN': deleting rrset at '222.1.168.192.in-addr.arpa' PTR
Mar 30 06:45:09 localhost named[20324]: client 127.0.0.1#46006: updating zone '1.168.192.in-addr.arpa/IN': adding an RR at '222.1.168.192.in-addr.arpa' PTR
Mar 30 06:45:09 localhost dhcpd: added reverse map from 222.1.168.192.in-addr.arpa to tgagne2.home.lan
Mar 30 06:45:09 localhost dhcpd: DHCPREQUEST for 192.168.1.222 (192.168.1.10) from 00:12:79:bf:f0:e2 (tgagne2) via eth0
Mar 30 06:45:09 localhost dhcpd: DHCPACK on 192.168.1.222 to 00:12:79:bf:f0:e2 (tgagne2) via eth0

And exactly an hour later, here's where it's lost:

Mar 30 07:45:09 localhost named[20324]: client 127.0.0.1#35153: signer "ddnskey" approved
Mar 30 07:45:09 localhost named[20324]: client 127.0.0.1#35153: updating zone 'home.lan/IN': deleting an RR
Mar 30 07:45:09 localhost dhcpd: if tgagne2.home.lan IN TXT "003773888aaec9f409727dde25e79c7e0e" rrset exists and tgagne2.home.lan IN A 192.168.1.222 rrset exists delete tgagne2.home.lan IN A 192.168.1.222: success.
Mar 30 07:45:09 localhost named[20324]: client 127.0.0.1#54559: signer "ddnskey" approved
Mar 30 07:45:09 localhost named[20324]: client 127.0.0.1#54559: updating zone 'home.lan/IN': deleting an RR
Mar 30 07:45:09 localhost dhcpd: if tgagne2.home.lan IN A rrset doesn't exist and tgagne2.home.lan IN AAAA rrset doesn't exist delete tgagne2.home.lan IN TXT "003773888aaec9f409727dde25e79c7e0e": success.
Mar 30 07:45:09 localhost named[20324]: client 127.0.0.1#38047: signer "ddnskey" approved
Mar 30 07:45:09 localhost named[20324]: client 127.0.0.1#38047: updating zone '1.168.192.in-addr.arpa/IN': deleting rrset at '222.1.168.192.in-addr.arpa' PTR
Mar 30 07:45:09 localhost dhcpd: removed reverse map on 222.1.168.192.in-addr.arpa
Mar 30 07:45:09 localhost dhcpd: Wrote 0 deleted host decls to leases file.
Mar 30 07:45:09 localhost dhcpd: Wrote 0 new dynamic host decls to leases file.
Mar 30 07:45:09 localhost dhcpd: Wrote 7 leases to leases file.

All my other hosts seem to work fine.

I've never seen an "if" statement show up from dhcpd so this is new to me.

[cpg]

this is ddns in action (dynamic dns, not to be confused with dyndns - a whole different thing).

there is no reason your hda would initiate this - i believe it's all initiated by the client.

does it happen with other clients??

i have seen conflicts with laptops trying to get two instances of the same name via wired and wireless interfaces (only one can win), but this is different.

maybe the wifi signal was weak?

does it happene very time at exactly one hour after the lease is granted?
dhcp has a fudge factor, so it's never exactly one hour.

maybe the laptop goes to sleep after an hour?

this just seems client initiated. i.e. a client issue.