When the lease-time gets changed on the DHCP-server, dhcpcd ignores these changes and uses the first lease-time always: 1. configure server to send lease-time of 86400s 2. start dhcpcd (-->will renew in 43200s) 3. reconfigure server to lease-time of 10800s (3h) 4. strace -p `pidof dhcpcd` # (leads to a renew) | alarm(43200) = 75595 --> uses still 43200 seconds (sniffing the traffic shows that dhcp-option 51 is set to 3h) This is a nasty bug when used with dynamic DNS updates. Then the host loses its A and PTR records for some hours, because server deletes them after 3h but the clients renews them after 12h.
Hi, Please test against the dhcpcd-1.3.21pl1 in rawhide, and see if this problem still occurs.
Problem still exists...
After you changed the lease time on the server, did you have dhcpcd renew the lease? Just a glaring omission that seemed rather obvious. There should be a new dhcpcd in rawhide soon that might be worth trying out if the renewal still uses the old lease time.