Feature request: Display block reason for blocked queries in the web interface

[gtech-pedrol]

Feature request

Description

When query logging is enabled in modDNS, the web interface currently shows that a query was blocked, but it does not show the reason for the block.

At the moment, I have to export the full JSON log data and inspect it manually to understand why a query was blocked. This makes troubleshooting slower and more cumbersome than it needs to be.

This is especially inconvenient when trying to determine whether a query was blocked by a specific blocklist, a custom deny rule, a security rule, or another filtering source.

Describe the solution you'd like

When query logging is enabled, I would like the web interface to display the reason why a query was blocked directly in the query log view.

For example, for blocked entries, it would be helpful to show:

• which blocklist triggered the block
• whether it was blocked by a custom deny rule
• whether it was blocked by a security-related rule
• any other available block source / reason already present in the logged data

This could be shown as:

• a dedicated "Block reason" column
• a tooltip
• an expandable details view
• or any similar UI element

The main goal is to make the reason visible in the web interface without requiring a manual JSON export and analysis.

Describe alternatives you've considered

The current workaround is to export the full JSON logs and inspect them manually.

While this works, it is not convenient for normal troubleshooting and makes it harder to quickly understand why a domain was blocked.

Another partial workaround would be to temporarily disable blocklists or rules one by one, but that is inefficient and not practical when multiple filters are active.

[MaciejTe]

@gtech-pedrol Thanks for the suggestion. This and similar diagnostic tools (e.g. a DNS query tester) are on our feature list. We plan to address these, and I'll update you here once they're live in production.

[gorkapernas]

Verified on staging. I tested the block reasons displayed in the Logs query cards for Blocklists, Services, and Custom Rules.

Based on testing and clarification from the implementation, this is the current behavior:

• If a domain matches a Custom Rule, that rule is shown as the block reason instead of any matching Blocklists or Services, since it represents the user's explicit configuration, so Custom Rules take precedence over Blocklists and Services.
• When multiple Blocklists could match the same domain, only one blocklist is currently displayed as block reason. From testing, this can appear as if certain blocklists take priority over others, but the proxy stops at the first matching blocklist in the active profile rather than collecting every match.
• Blocklists and Services are treated with the same blocking priority. If both apply to the same domain, both block reasons may be displayed together. This is why, both a Blocklist and a Service can be shown for the same query.

This should be good to go.