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

Allow specifying block response in configuration #58

Merged
merged 1 commit into from
May 13, 2024

Conversation

mutemule
Copy link
Contributor

NXDOMAIN is the traditional response code for blocking DNS queries, but can make it difficult to differentiate between actual DNS problems and DNS blocklists. This change introduces the ability to respond with REFUSED instead, to make it easier to identify DNS blocks.

The default behaviour remains to respond with NXDOMAIN, so no additional configuration is required to maintain current behaviour.

@relekang
Copy link
Owner

This is great. Is there anything else you were planning to do since it is marked as draft or should we merge it?

@mutemule
Copy link
Contributor Author

I need to update the examples and then give this a look over with some fresh eyes! Should be ready shortly.

@mutemule mutemule force-pushed the error_code_configuration branch from d319d90 to ab632b6 Compare May 11, 2024 12:41
@mutemule mutemule marked this pull request as ready for review May 11, 2024 12:42
@mutemule
Copy link
Contributor Author

Added a couple of tests to check failure modes, which wound up finding a problem (blockResponse := remaining[0] vs blockResponse = remaining[0]). It's fixed now, and this should be ready!

NXDOMAIN is the traditional response code for blocking DNS queries, but
can make it difficult to differentiate between actual DNS problems and
DNS blocklists. This change introduces the ability to respond with
REFUSED instead, to make it easier to identify DNS blocks.

The default behaviour remains to respond with NXDOMAIN, so no additional
configuration is required to maintain current behaviour.
@mutemule mutemule force-pushed the error_code_configuration branch from ab632b6 to 5f0f6e7 Compare May 11, 2024 12:43
@relekang
Copy link
Owner

Nice 👍

@relekang relekang merged commit 40f0825 into relekang:master May 13, 2024
@relekang
Copy link
Owner

I forgot to tag it after it was merged, but it is tagged and built now: v1.12.0

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

Successfully merging this pull request may close these issues.

2 participants