Hi, any update with this bug? suppose there has not been any fix yet?
The suggested workaround isn't really feasible in reality when there are dependencies on FQDNs in a hybrid environment with many AWS/Azure based VMs.
Symptom: Traffic does not match an ACP rule which has more than one FQDN object specified as source or destination networks. Instead, another rule below will be matched.
Conditions: 1) An ACP rule is configured with more than one FQDN object as a matching condition. 2) There are no IP-based objects in source or destination networks.
Workaround: For FQDN-based rules specify only one FQDN object. If needed, create a separate rule for every FQDN that should be matched.
