Paloalto cannot resolve specific FQDN through Nslookup & "fqdn refresh" is not working on CLI console

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Please sign in to see details of an important advisory in our Customer Advisories area.

Paloalto cannot resolve specific FQDN through Nslookup & "fqdn refresh" is not working on CLI console

L3 Networker

Hello all,
Our client company uses FQDN A and B that Nslookup the same IP, and the firewall has a DNS access policy applied with these FQDN.

Recently, the customer deleted the DNS of B, and if it is normal operation, it should be normal service with FQDN of A, but DNS blocking issue occurred.

In addition, entering FQDN refresh from the CLI does not apply, and only when a commit is made through the GUI, the IP permit policy lookup to domain B of the actual device is applied.

It is confirmed that the policy is applied after committing through the GUI console, but I want to know why it is not applied when you try "fqdn refresh" in the CLI.

I tried to run "request system fqdn refresh force yes", but it was not working.

Best and Regards,


Community Team Member

Hi @JoHyeonJae ,


Hard to say what caused it with the information at hand but maybe the FQDN refresh job was failing:


FQDN Refresh Job Fails 


Kind regards,


LIVEcommunity team member, CISSP
Please help out other users and “Accept as Solution” if a post helps solve your problem !

Read more about how and why to accept solutions.

Hi @kiwi 

I think FQDN reload does not appear to have failed. Because the output related to FQDN refresh could not be found in the result of show jobs all.

Show jobs all -> there is no any FQDN refresh log like FQDN refresh failed, FQDN Refresh job successful, and so on.

  • 2 replies
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

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!