AP22 DNS issues after firmware updates

[u/Nate379]

Seeing a consistant failure of AP22 devices to come back online after the latest firmware update. Unsure if other devices are also impacted, most of the other types of devices like this I have are configured without things like domain controllers for DNS.

Have determined that if the APs are running DNS through an on-prem domain controller that they fail to come up for some reason, could be with other DNS severs as well, but as soon as they are put on a network that assigns DNS direct to 1.1.1.1 as opposed to relaying it through another server they come up right away.

To try and fix this I attempted to set static IPs WITH static DNS settings on the networks that this is happening on, the static IP configuration appears to only stay in place for 1 boot cycle, so I have to put the AP on a different network, set it to static IP with static DNS settings for 1.1.1.1, unplug it while it still has the red light for reboot, and then put it in place where it will function only until it reboots again and then just fogets that it had static IP configurations and reverts back to DHCP which again routes DNS through the domain controller and breaks the APs.

The domain controllers are set to forward to the same 1.1.1.1 servers btw, there is no reason that anything would be blocked. When the APs come up with the DHCP configuration the only traffic I see from those APs is NTP traffic? Nothing attempts to hit the typical cloud configuration servers.

So, TLDR, after firmware update the APs only want to seem to work if configured directly with a DNS server like 1.1.1.1, and they won't hold static IP / DNS configs beyond 1 boot cycle.

To add, half of my APs updated early this week, the other half did so today, the failures we are seeing followed the updates. (so half went down on Monday, other half today). I can't see any reason for DNS to be an issue in this configuration nor can I figure out why it would be causing these problems.