Handling Web Site Not Resolved by DNS

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.

Handling Web Site Not Resolved by DNS

L3 Networker


   Anyone handling DNS Resolution Failures - user types bad url or site not available?

   Would appreciate hearing your ideas...




L6 Presenter

If you mean security wise you can always use whitelisting.

If the user typed the url correctly and the url is part of the categories you are allowing the user will be able to visit the site - otherwise the request will be blocked.

L4 Transporter

Are you seeing Not Resolved, in your list of URLs? It may be because your local URL db does not have the category for that URL. If so, the URL is usually checked against the Cloud Servers for the correct categorization. To get categorizations from the cloud please go to "Objects>>URL FiIltering Profile>> Choose the profile attached to the security policy and ensure that the "Dynamic URL Filtering box is checked. This should get URL resolutions for links that are not known through the local URL DB

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