Discussions
Feature Request: Per-Rule Block Response Override in Custom Rules
17 hours ago
Problem:
The Block Response setting is currently global to the Profile. This creates issues when different blocked endpoints require different handling—such as returning NXDOMAIN to prevent socket timeouts on specific services, or sinkholing a domain to an internal IP (block page) without forcing that behavior across the entire Profile.
Proposed Solution:
Add a "Block Response" override dropdown inside the Custom Rule modal when the action is set to BLOCK (Inherit Profile Default, 0.0.0.0, NXDOMAIN, REFUSED, or Custom IP). The Activity Log should continue reporting these queries as BLOCKED while noting (extra) the synthesized response returned to the client.