You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
I am running the latest version
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed
Problem Description
Handling per client rules in custom rules is possible, but not too handy in practice due to the complex rule expressions.
The list of services defined is short, and not extendable.
Proposed Solution
Allow users to extend the internal/dnsfilter/blocked.go serviceRulesArray with custom definitions, even better if this can be consumed like the block list itself, aka based on a feed.
Specific use-case, blocking CDN access to any CSS JS etc static lib which with browser plugin can be injected back into cache so page functionality does not break, hence it can be blocked on DNS level, but for clients where this is not an option, this "service" should be enabled, OR an other specific use-case is connectivity check endpoints, most of the device talk home with performing "am I online" connectivity checks, this can be by default blocked, but some devices will just drop the connection if they don't "think" that they are online, so having this defined as a service, would make it easy to switch on and off.
Alternatives Considered
The current way to do this now, is use labels, and label specific rules, which works ™️ but pretty complex to handle.
Additional Information
Icons, and etc in case custom service definitions can be generic.
The text was updated successfully, but these errors were encountered:
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Problem Description
Handling per client rules in custom rules is possible, but not too handy in practice due to the complex rule expressions.
The list of services defined is short, and not extendable.
Proposed Solution
Allow users to extend the
internal/dnsfilter/blocked.go
serviceRulesArray with custom definitions, even better if this can be consumed like the block list itself, aka based on a feed.Specific use-case, blocking CDN access to any CSS JS etc static lib which with browser plugin can be injected back into cache so page functionality does not break, hence it can be blocked on DNS level, but for clients where this is not an option, this "service" should be enabled, OR an other specific use-case is connectivity check endpoints, most of the device talk home with performing "am I online" connectivity checks, this can be by default blocked, but some devices will just drop the connection if they don't "think" that they are online, so having this defined as a service, would make it easy to switch on and off.
Alternatives Considered
The current way to do this now, is use labels, and label specific rules, which works ™️ but pretty complex to handle.
Additional Information
Icons, and etc in case custom service definitions can be generic.
The text was updated successfully, but these errors were encountered: