Everything on this VLAN is static assigned with no DHCP. I have other VLANs for local LAN and Wireless that transverse a Cisco Router. The router has relay agents on the sub-interfaces to my Windows Server 2022 Active Directory Server also doing DNS and DHCP for these network. The devices have reservations inside DHCP. Untrusted Wireless is going through Cisco ASA. Cisco WLC 5508 is providing DHCP for this VLAN but after initial devices are added they also get a reservation DHCP address. There are no logs on any of the Cisco equipment related to Layer 3 changes. DHCP is only used for new devices that I add just to L3 connectivity then moved to specific range in the VLAN. Only 3 addresses are active per VLAN and do not communicate with anything until I make a firewall change for http, https or ssh. Even if DHCP would have taken over I would have had more problems.
Noticed PRTG server shows communication loss to the MBP DNS name from around the time I noticed the system name being changed randomly. IP Address was still showing active. The error went away after changing the system name again. Actually was ignoring the PRTG server errors thinking it was something to do with the VCF environment I was creating.
The problem is Red Hat OpenShift Container Platform relies solely on DNS. In this VLAN / LAB, communication stopped with the YAML Server and the environment inside the MBP. The Application Firewall did not like that he name and IP Address did not match but after changing the name back everything was worked.
Over all it is the MBP changing the system hostname that is causing the problem. Saturday evening the name changed on its own again saying a new interface was detected. Nothing was added and DNS resolution stopped. After a reboot I was able to change the name back and continue. Not sure why this is happening now. Seem since a couple updates back it started to occur.
Would there be something in iCloud that would be causing the problem? Couple updates ago iCloud process started to hang. Having to kill it and then run "killall bird" to sync again. It was fixed before sometime back but happening again. Just a thought.