If you look closely, you can see the IP address changes from 10.166.81.241 to 10.166.81.240. Here is the log output (after turning on debug) for DHCP and systemd-networkd. This is a new thing for us DHCP with Infoblox. The Data Management -> DHCP -> Leases tab shows a ton of entries that are no longer relevant. I suppose I shouldn't fret over all that information, but it seems to be that it is clutter that would best disappear when no longer needed. The MAC ADDRESS and DHCP CLIENT IDENTIFIER columns show the same information for all of the previous leases. The FINGERPRINT column shows "no match" for the active lease. The old IP addresses still show the host name, but they are showing "Used" in the STATUS column under IPAM (though that seems to be case for all the entire DHCP Range) and "Free" in the LEASE STATE column. Am I missing something in my configuration somewhere? Or is this expected behavior? How do I prevent it from making an IP change on reboot without having to go into Infoblox everytime I set up a server? Keep in mind, the vast majority of people spinning up these resources don't necessarily have access to Infoblox (at least that it the use case we are going after). The MAC is still the same in both instances, but the host was shifted down to the next available IP address in the range as opposed to reusing the same IP address. However, if I reboot the server (as I just did for a kernel update), the IP address changes. My host gets an IP address just fine and it even sets the DDNS. I recently created a new network segment, enabled it for DHCP, setup my DHCP Range, setup DDNS, and restarted the services. I'll continue to search the forums, but I am hoping somebody can shed some light on what I'm seeing.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
December 2022
Categories |