Repository navigation
Fix Control D endpoints to use the p1 filtering profile - #12
Merged
Merged
Conversation
The Control D entries were labelled "Blocks malware (p0 profile)" but addressed the p0 profile, which is unfiltered resolution. Switch the IPv4/IPv6 addresses, DoH URL and DoQ hostname to p1 so the endpoints match their advertised behaviour, and bump the version to 0.7.1.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The seven built-in Control D endpoints were all labelled
Blocks malware (p0 profile), but they were addressed at the p0 profile — Control D's unfiltered resolver. Anyone benchmarking these entries was measuring plain recursive resolution while the tool claimed they filtered malware, and any resolver picked from those results would not have blocked anything once configured.This switches every Control D entry to the p1 profile, which is the one that actually blocks malware, so the addresses match their advertised behaviour.
Changes
internal/serverlist/builtin_servers.json76.76.2.0→76.76.2.1,76.76.10.0→76.76.10.12606:1a40::→2606:1a40::1,2606:1a40:1::→2606:1a40:1::1https://freedns.controld.com/p0→.../p1p0.freedns.controld.com→p1.freedns.controld.comp0top1internal/model/model.go: version bumped to0.7.1Server IDs are left untouched so existing user configs that reference them keep working. The endpoint count stays at 57.
Verification
go build ./...andgo test ./...— all packages passdig @76.76.2.1 example.comanddig @76.76.10.1 example.comanswer correctlyhttps://freedns.controld.com/p1returns200for a DNS-JSON query