Start Dhcp not updating lease

Dhcp not updating lease

Below log confirms the renewal happens every defined interval, Apr 29 dhclient[12270]: DHCPREQUEST on mgmt1 to 192.168.10.2 port 67 (xid=0x2b10e716)Apr 29 dhclient[12270]: DHCPACK from 192.168.10.2 (xid=0x2b10e716)Apr 29 dhclient[12270]: bound to 192.1 -- renewal in 31 seconds.[[email protected]]# cat /var/lib/dhclient/dhclient-mgmt1.leaseslease Lease file updation happens properly after the defined expiry interval, but the problem is with classless-static-routes, if there is any change with the parameter ("classless-static-routes" new gateway) leases file holds the updated information but not the routing table, can see that from the below table:[[email protected]]# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface169.254.169.254 255.255.255.255 UGH 0 0 0 mgmt1Leases file hold the updated information but routing table is not aware of the change happened within the existing route.

How can the DHCP be configured to refresh the DNS records after a given time interval?

Hi all, I'm new to this forum, please correct me if I'm wrong somewhere below.

I run a dhcp-server and push the static routes to the clients, could see routes on the routing table but the problem is with the partial updation on the existing routes.

I have an Iogear usb wifi in my rpi, that connects just fine with my d-link router. If I ifdown/ifup wlan0, it also gets an IP address via DHCP.

And if I enter dhclient -v wlan0 while the lease is still up, that appears to work as well, according to the output.

Complete a brief survey to get a complimentary 70-page whitepaper featuring the best methods and solutions for your virtual environment, as well as hypervisor-specific management advice from Tech Target experts.

ddns-updates on; ddns-update-style standard; update-conflict-detection false; allow client-updates; ddns-domainname "local.domain.com"; ddns-rev-domainname ""; update-static-leases true; default-lease-time 7200; max-lease-time 7200; authoritative; [...] Whenever a client gets a new IP from the DHCP, the DNS registration works perfectly.

For testing purpose, I had set the lease expiry to minimal time.