dhcp failover relationship errors for mulitple domains.
I'm getting a similar issue with this link below.
It looks like Microsoft never looked into or have a way to work around DHCP servers outside of the domain that SCOM is in.
There are various reasons why SCOM is unable to access a dhcp servers, firewall (because of security design), or different domains ( because of various requirements).
We should be able to move this monitor for the Windows Server 2016 DHCP Failover Relationships off of the main management servers (rms emulators) and onto another server like the gateway servers.