External ipaddress 220.127.116.11 is getting incorrectly mapped to a rule "Permit Intranet Sites".
The rule uses a Urlcategory for Intranet sites and the destination has trust/untrust zones with a negate on one specific destination address.
What might cause the firewall to misapply rules if the dns to ipaddress mappings are effectively static?
I also have noticed on more than a few instances of policies with UrlCategory being applied incorrectly, many of which are external ipaddresses.
Solved! Go to Solution.
URL filtering != FQDN. URL filtering is looking at what's in the packet headers, FQDN is permitting based on the resolved IP address.
If you make the question more tangible I can try and give a specific answer.
Have a good day,
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!
The Live Community thanks you for your participation!