After 4.15.4, Arch dhcpd clients on LAN get new IP, but zone update fails (server - bind w/dynamic update)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

After 4.15.4, Arch dhcpd clients on LAN get new IP, but zone update fails (server - bind w/dynamic update)

David C. Rankin
All,

  Not sure if this is kernel or dhcpcd related, but after update to 4.15.4
tonight ArchLinux clients on LAN receive new IP from server (which have not
changed in 4-years before), and server DNS zones are not updated, but instead
retain the old IP. The error is a general "Has an address record but no DHCID,
not mine." (which may be a holdover from an earlier bind failure)

  Regardless, this has never before caused dhcp4 to issue a new address while
retaining the old in the zone files for any Arch client in the 50 or so kernel
updates before 4.15.4. (and this was consistent for each Arch box after the
4.15.4 kernel update)

  Take it for what it is, just be aware if you are admining a remote Arch box
that gets its address via dhcp, you may end up with a new address while the
old is still reported by nslookup. Just strange...

  No replay necessary, unless you have an idea of what changed between 4.15.3
and 4.15.4 that may cause this behavior.

--
David C. Rankin, J.D.,P.E.