URL 9.0 URL Category Cache Build Time?


ATTENTION Customers, All Partners and Employees: The Customer Support Portal (CSP) will be undergoing maintenance and unavailable on Saturday, November 7, 2020, from 11 am to 11 pm PST. Please read our blog for more information.

L4 Transporter

URL 9.0 URL Category Cache Build Time?

How long does it take for the URL categories to build in the 9.0 release?   We have an issue with google-base app, where almost all google searches come back as the 'not-resolved' category for the first 5 minutes when we change datacenters.   8.1 you could just re-download the seed database, and we never had a problem.    


9.0 there isn't such a thing it appears.    Has anyone seen this type of activity before, or had to deal with a short time of not-resolved blocks, until 5 minutes later- the exact same google search will run normally?


Yes, our URL license is valid, and shows connected, and no service routes in place, or decryption  going on for management interfaces.

L1 Bithead

the url cache should get synced every 8 hours




you could try clearing your cache on both devices over the weekend in case something got 'stuck' and is preventing the sync

L4 Transporter




Thanks for your quick reply!  This is specific to a completely different set of firewalls at a different location, that all traffic would now be passing through. Not the same HA pair.     


The new pair doesn't yet have it's cache populated, so we see a bunch of drops due to not-resolved.    

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 Live Community as a whole!

The Live Community thanks you for your participation!