If you are using Cloudflare to connect to your Content Policy using Cloudflare WARP (Mac/Windows), Cloudflare One (Android/iOS), or manually configured (router or manual settings), this article will help you ensure your device is using Cloudflare's DNS.
First, go to dnsleaktest.com and run a standard test
Your results should only pull up results for Cloudflare in the ISP column.
If you see other entries, your connection is likely not configured properly or you have a "DNS Leak" where some, but not all, internet traffic is routed through Cloudflare.
If Cloudflare shows up as your ISP and the issue is still present, then it means that you likely have issues with your browser caching web browsing results or your Content Policy does not have block rules that match the test domains.
If the test results show you're connected to Cloudflare DNS, make sure to clear your device's cache, especially if you've visited the website before filtering was enabled.
Clearing a device's local DNS cache
For most smartphones:
- Turn on Airplane mode
- Force close any open browsers
- Turn off Airplane mode
For Windows computers, open Command Prompt as an Administrator and enter this command:
ipconfig /flushdns
For Mac computers, open Terminal and enter this command (type your Mac's password when prompted):
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
In some rare cases, you may need to completely restart your computer to force your cache to completely clear.
If you've taken all of these steps and the domain is still accessible, your browser is most likely caching the webpage. You may need to also clear your browser's cache and cookies to resolve the issue.