topic Re: Traffic stops hitting when one of two FQDN objects in policy not resolvable in General Topics

Traffic stops hitting when one of two FQDN objects in policy not resolvable

nikoo — Wed, 18 Jan 2023 13:41:32 GMT

There is a security rule with two FQDN objects used as destination. Along with that user group is configured and source/destination zones - nothing special.

There have been a couple of cases where traffic suddenly stops hitting the rule although everything seems to be in the place. It turns out on of the two FQDN address objects is not resolving anymore (which is fine as it was removed from the DNS) and as soon as removing that unresolvable object, traffic to other FQDN (which resolved just fine) destination started working and traffic hit the rule correctly.

Not sure if that was solved by really removing the unresolvable object or just committing something would do the trick as well (as in both cases commit included removing the object). Haven't been able to reproduce the issue yet.

Have someone seen something like this? Ideas?

Re: Traffic stops hitting when one of two FQDN objects in policy not resolvable

Adrian_Jensen — Wed, 18 Jan 2023 16:49:14 GMT

Which PANOS is this? I have multiple rules with multiple FQDN destination objects where one or more has expired and I haven't seen that behavior.

Re: Traffic stops hitting when one of two FQDN objects in policy not resolvable

nikoo — Wed, 18 Jan 2023 17:01:53 GMT

10.1.6-h3

This could be some combination of other aspects as by making such a setup intentionally (rule with expired FQDN object) I couldn't recreate the issue.