Content translations are temporarily unavailable due to site maintenance. We apologize for any inconvenience. Visit our blog to learn more.
01-10-2019 10:57 AM
I wanted to reach out tot he community and see how people are handling FQDN cache limit issues.
Example:
* Internal DNS caches up to 8 IPs for each FQDN
* PAN device will cache up to 10 (source: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClHJCA0)
If you have a security policy that allows traffic to blah.domain.com and that FQDN is in AWS and could be 20/30/100 IPs your traffic will not always hit the policy allowing the traffic you want to allow since the IP address the application happens to hit will not always be in the FQDN cache.
possible solution #1: have the vendor add more FQDNs (good luck)
possible solution #2: manually add a ton of IPs to the security policy (horrible idea)
possible solution #3: leave it alone and accept that the application will try again and eventually hit an IP that is cached
possible solution #4: Ask the vendor to use a load balancer (good luck)
possible solution #5: ?
Anyone else run into this? I know there has to be a limit somewhere but I can see this being more and more of an issue as things are moved into the cloud.
