ā11-21-2024 04:56 AM
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.
ā11-21-2024 05:39 AM
- The bug report refers to https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwj24828
which has fixed versions ,
M.
ā11-21-2024 05:45 AM - edited ā11-21-2024 05:45 AM
Thanks, I've looked at that earlier but that's for a similar bug and not the one we are after. And fixed versions don't include FTD software.
ā11-21-2024 06:15 AM
Workaround is not work for you??
Also did you try DNS SI ?
In DNS SI you can specify all domain
MHM
ā11-21-2024 06:24 AM
we've got a loads of hosts in AWS and Azure, so not realistic approach for us.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide