We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.
Barracuda Web Security Gateway

Why isn't my Barracuda Web Filter working when configured to block all HTTPS traffic?

  • Type: Knowledgebase
  • Date changed: 10 years ago
Solution #00003204

Scope:
All Barracuda Web Filters, firmware versions 3.3.03 and above.

Answer:
When first enabling HTTPS filtering, any client PCs that had previously established an HTTPS session will not be blocked. In this situation, the HTTPS website's IP address remains in the user's local DNS cache (as well as in the DNS table on the core router or domain controller) until the DNS request time-to-live (TTL) expires. This can take up to a day or two, depending upon how the HTTPS sites configure TTL. What this means is that until the user performs another DNS lookup of a website's domain name, the Barracuda Web Filter won't automatically know which domain is associated with the IP address and won't be able to perform any domain blocks on those connections.

To hurry this along, you can manually clear the DNS cache on your network's DNS servers.

Additional Notes:
For more information on the Barracuda Web Filter and HTTPS filtering, see Solution #00003316.

Link to This Page:
https://campus.barracuda.com/solution/50160000000H7kKAAS