Troubleshoot File Inspection

When File Inspection is enabled, and Umbrella does not raise a block page when expected, ensure that the DNS policy or Web policy ruleset with File Inspection enabled is higher in the policy order than other DNS policies or Web policy rulesets that the identities are configured for.

Wait upwards of five minutes before testing again after any policy changes to ensure enough time has passed for the changes to be replicated throughout the Umbrella infrastructure. If problems persist, try clearing the local browser cache on your machine, or even your machine's DNS cache (a reboot will accomplish this).

Check to see if you have a local on-prem proxy that is interfering. For more information, see Using Umbrella with an HTTP proxy.

Confirm that a root certificate is installed. For more information, see Manage Certificates.

Help

If you encounter an unresolvable issue with File Inspection, contact Support.

You may want to include the output of the following commands run from a device enrolled in the policy configured for File Inspection:

OS X
dig proxy.opendnstest.com
dig debug.opendns.com txt

Windows
nslookup proxy.opendnstest.com
nslookup -type=txt debug.opendns.com

We also recommend including the output of the Umbrella diagnostic tool. See Umbrella Diagnostic Tool.

---

Test File Inspection < Troubleshoot File Inspection > Manage File Type Control