Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] RFC8914 EDE Extended DNS Errors for RPZ #1191

Open
mdavids opened this issue Nov 25, 2024 · 0 comments
Open

[FR] RFC8914 EDE Extended DNS Errors for RPZ #1191

mdavids opened this issue Nov 25, 2024 · 0 comments

Comments

@mdavids
Copy link

mdavids commented Nov 25, 2024

Current behavior
When RPZ kicks in, no related EDE is included.

Describe the desired feature
When RPZ kicks in, an appropriate (configurable?) EDE is included. In particular one of the codes 15 (blocked) , 16 (censored) , 17 (filtered).

Potential use-case
Users of an Unbound resolver don't get clear feedback of an RPZ-action. For example if a domain name is blocked due to EU sanctions, they might get an NXDOMAIN and nothing more. An EDE of 16 would greatly help them understand what is actually happening.

One suggestion for achieving this, is to introduce additional action options, like:

CNAME ede16. for NXDOMAIN with EDE16

CNAME *-ede16. for NODATA with EDE16

But there may be other ways to accomplish something similar, for example by adding configuration options, such as rpz-signal-nxdomain-ede16. Or perhaps something with tags?

I'd like to leave it to the developers to think of the best way to provide such a feature to Unbound.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant