We are seeing this occur with 802.1X machine authentication fairly
consistently upon upgrading to 10.15.2. The AP logs show that the
machine is attempting to use the first part of the AD domain's FQDN
instead of the domain's NetBIOS name in "domainus...
At one point we ran into an issue where we had multiple profiles with
Restrictions payloads scoped to a particular iPad and ASAM was failing
to take effect. At that time, we found that if there were any profiles
with Restrictions payloads on the iPad...