It seems to me that web caching is getting auto-enabled when web filtering is on, despite the fact that I don't have the feature enabled in the GUI.
We do a lot of web development work with external clients, and this often involves migration to new hosting facilities and, consequently, DNS changes to re-point domain names to the new IP addresses. Once a site migration/upgrade has been carried out, and DNS has been updated, we will clear the DNS caches at various levels so that we can view the change--rather than wait for the various cached records to reach their TTL.
DNS resolution in our network: Our local machines are pointed at the domain controllers, which are pointed at the UTM, which points to a DNS group composed of OpenDNS servers. In other words, we use best practices as outlined elsewhere in this forum.
The problem is this: It happens that even after DNS caches are flushed on local PC, DCs, and the UTM, and pings to the web domain name show the updated/correct IP address, the old website still shows up in the browser.
My first thought was that the browser must be caching the old site. But no, even when the browser cache is cleared, browser is restarted, a different browser is used, or a different PC is used, the old site still shows. But, if I then go into the UTM Webadmin and disable Web Filtering, the correct website will show in the browser.
Thoughts, anyone? Am I missing something, or have I discovered a (very glaring) bug?
This thread was automatically locked due to age.
