On a Palo Alto Firewall, we created an address object using FQDN Type.
We use this object as a destination address in the security rule « TEST-FQDN-1 »
But checking the security policy (show running security-policy) we can see the destination is not resolved (destination 0.0.0.0;)
And checking the fqdn entries (system fqdn show) we can see the FQDN is in a « Not Resolved » status.
We tried to ping the host from the firewall and the ping well resolve the address so it looks like the DNS configuration is OK
We also tried to refresh FQDN entries (request system fqdn refresh) but it doesn’t change anything.
Do we miss something ? Do we have to add some more configuration ?
We are having this exact same issue, only on 4.1.12 and using lower-case. (Perhaps I should have created a new thread for this given that the original post is now two years old, but Hub described it so well I didn't see a reason to duplicate the effort )
The problem is only affecting a single address object, and in the FDQN logs it shows as "not resolved". Other similar entries are resolving correctly. What's odd is that this was working when originally configured some weeks ago. The firewall is able to ping the address by name, so name resolution is working. The problem entry is outlook.office365.com which is a mix of both IPv6 and IPv4 addresses.
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!