Troubleshooting traffic being blocked based on IP - FQDN rules

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.

Troubleshooting traffic being blocked based on IP - FQDN rules

L2 Linker

Trying to find which FQDN object in my FQDN cache resolves to an IP.

show dns-proxy fqdn all | match <ip> shows me that it's in my cache, but doesn't show FQDN object name, so it doesn't really help.


I'm not sure if there's a way to dump this to a file or something or a more straight forward way to do this.

Any insights is appreciated.





L6 Presenter

"show dns-cache fqdn all" shows you all the address objects and their resolved IPs. Unfortunately, as you discovered, the object name and resolved addresses are on sequential lines... So if you use a "match" operator you only match the IP line, not the preceding object name line. Even more unfortunately, address objects are not displayed in any discernable order.. .so its even harder to find.


The only "easy" way I've found to do it is to do a "show dns-cache fqdn all" and paste the output into notepad, then find the IP from there and look at the preceding address object name. Alternatively you could probably query all the address objects via the API and filter/return a match, but you would need to write a script in your language of choice to do that.

Thanks Adrian, so far that's the conclusion I came to as well, which is kind of limited for the product in my opinion that's a lot of leg work for something that can happen regularly.

  • 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!