05-16-2020 06:45 PM
I created a new FQDN address object to facilitate a new Policy(rule).
When tested the FQDN resolves internal to the Palo Alto Firewall.
The rule contains one destination address which is the new company.fqdn.com FQDN
The rule contains one source address
Application SSL with Application-Default Service
When attempts are made to connect to this destination via the new rule with the FQDN set(destination), the traffic is denied(fails) and logs point to(identify) the "interzone-default" rule instead of the "new rule" that is set up to facilitate this connection
But when I replace the FQDN(destination) with it's resolved IP in the new rule, it works fine(allowed) and logs point the occurrence to the "new rule" (not the interzone-default) as to be expected since that is normal behavior
Thanks in advance.
06-13-2022 11:58 PM
We are also having a similar problem with the FQDN in an address object.
For a given fqdn, the result of nslookup is different from "show dns-proxy fqdn all" which is also different from the "resolve" of the fqdn in the address object of the gui.
Other fqdn's appear to work OK, but the associated IP's may be static and the IP list much shorter.
We are using DNS Proxy and the cache is activated. We had TTL activated as well, but i've removed it as its not necessary.
Shall we try deleting the address object and recreating? How can we resolve this?
06-14-2022 12:21 AM
I also tried the fqdn force refresh command, to no avail.
However, I just saw this article that states that only "up to 32 addresses" are mapped to an FQDN used in an address object: https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA10g000000ClHJCA0
So, what does this mean for the fqdn we are using? edge-teams.plcm.vc (https://mxtoolbox.com/SuperTool.aspx?action=a%3aedge-teams.plcm.vc&run=toolpage) - goes way over the 32 limit.
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 LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!