FQDN not resolved

[Hub]

Hi

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;)

TEST-FQDN-1 {

        from any;

        source any;

        source-region any;

        to Trust;

        destination 0.0.0.0;

        destination-region any;

        user any;

        application/service any/any/any/any;

      action allow;

}

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 ?

Please help

Thank you

Hubert

[Hub]

Problème résolu

[singersit]

Hi There,

Are you able to share the resolution to this issue?

[migration]

You should post the resolution so everyone benefits.

[singersit]

I managed to work this out....

We were using UPPERCASE FQDN objects, changed them to lowercase and all is good

[migration]

I see.

[Jamiefitzgerald]

Which software version were you using?  Was the object name capitalized, or the actual FQDN address?

[Hub]

Hi everybody,

The Palo Alto has some problem to resolve object name in uppercase.

Palo Alto confirmed that they will fix this bug in version 4.0.5.

Until, you may use lowercase object name and it will work.

Hubert

[Jamiefitzgerald]

This is a known issue that will be solved in 4.0.5.  The issue is not the object name, it is the the URL itself that cannot be capitalized.

[KGC]

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.