Review Gateway blocks
You can use Cloudflare Gateway to filter and log DNS queries from devices on any network. You can also use Cloudflare Radar to review why a site has been blocked.
🗺️ This tutorial covers how to:
- Review DNS filtering logs in Cloudflare Gateway
- Review the reason a domain was blocked in Cloudflare Radar
- Submit categorization feedback
⏲️Time to complete:
5 minutes
Before you start
- Add Gateway to your account
- Deploy Gateway rules to a network or group of devices
Review Gateway events
In this example, a Cloudflare Gateway DNS filtering rule has been applied to all locations to block social media.
Once deployed, Cloudflare Gateway will begin to block DNS queries to sites categorized by Cloudflare as social media networks. You can review each block in the Zero Trust dashboard.
Navigate to the Logs section of the sidebar and choose Gateway.
Click the Filter action to filter by date range, user, action, and policy. In this example, choose Blocked as the action taken.
You can expand the record to identify more information about the event, including user identity if you have deployed the Zero Trust agent .
Review block reason
Review details about the domain blocked by Cloudflare by clicking View domain details in Radar. Cloudflare Radar provides information like site ranking, certificate history, and WHOIS information. If you believe the site was not categorized appropriately, click Submit Categorization Feedback beneath the Content Categories section.
Override a rule
If you need to allow a specific hostname that was blocked as part of a larger group, you can create an exception in Cloudflare Gateway.
Return to the Policies page in the Gateway section. Add a new policy by clicking Create a policy.
Choose DNS Domain and input the domain to be allowed as the value. Select Allow as the action and create the policy.
Cloudflare Gateway enforces policies in an order from top-to-bottom. Drag the new policy to the top of the list.
Once added to the top of the list, DNS queries to this host will be allowed based on the first matching rule before DNS queries to other social media sites are blocked with the subsequent rules.
