Discussions

I’ve recently signed up for the service. Primarily it’s great as an ad-blocker, but the Geoblocking service is a little broken for a couple of services I’ve tried.

Is website selling wines meant be blocked by drug filters?

I can see this being useful if any of my endpoints or clients trigger the Malware filter (I would want to know so I can quickly quarantine), or if e.g., a teenagers client device tries to access illegal/restricted websites.

Hello,

Hello.
Greetings.
Would it be possible to add a third-party gambling blocklist?
Specifically this one:

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.

Would be great for schools and younger children.

It would be nice if there was a flag/etc to override this behavior and specify a specific upstream for LAN Queries (specifically, bare host queries without a domain - e.g. machine1, machines2). For my use case, all bare queries should go to dnsmasq on a router listening on port 53053. CTRLD lives in a docker container on a separate VM, and all clients point to that address:53.

DFBPlay.tv streams the matches of the DFB Pokal for free in foreign countries outside of Germany like UK. I implemented the needed rules successfully as my custom rule i want to share.

Currently, when a Control D profile is used in a "monitoring mode" (where traffic is fully allowed), the analytics dashboard only displays the raw domains visited. While explicitly adding Native Services in "Bypass/Allow" mode maps service names to the analytics logs, this metadata is entirely missing for native Web Filtering Categories.I would like to request that Web Filtering Categories also be mapped and displayed within profile analytics when running a passive monitoring policy. This could be achieved by introducing an explicit "Allow/Monitor" action state directly within the Native Categories settings, or by creating a dedicated global "Monitoring Mode" switch at the profile level.
Secondary Benefit: Introducing an explicit "Allow" action for Native Categories would also provide helpful, granular override capabilities for administrators utilizing a strict, block-by-default profile posture.