Repository navigation
Mark Quad9's unfiltered upstream as validating DNSSEC - #3284
Merged
Merged
Conversation
Quad9 validates DNSSEC on all of its service endpoints, including the unfiltered `9.9.9.10` set, so the "no DNSSEC" label in the upstream server list is wrong. Signed-off-by: DL6ER <dl6er@dl6er.de>
This was referenced Oct 23, 2026
yubiuser
approved these changes
Oct 23, 2026
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.
What does this implement/fix?
Quad9 validates DNSSEC on all of its service endpoints now, including the unfiltered
9.9.9.10set (see their service addresses page). The upstream list FTL hands to the web interface still labeled it "no DNSSEC".The installer list and the docs carry the same label and are fixed in pi-hole/pi-hole#6740 and pi-hole/docs#1442.
How to test the change during review
dig @9.9.9.10 dnssec-failed.orgreturnsSERVFAILanddig @9.9.9.10 isc.orgcarries theadflag. The same holds for149.112.112.10,2620:fe::10and2620:fe::fe:10.The name is a display label only, nothing matches on it, so there is no test change.
Additional information
Related issue or feature (if applicable): Fixes #3280
Pull request in docs with documentation (if applicable): pi-hole/docs#1442
By submitting this pull request, I confirm the following:
git rebase)src/dnsmasq/. That tree is a verbatim copy of upstream dnsmasq and we do not carry anything in it that deviates from upstream. Fixes have to go through thednsmasq-discussmailing list first, we merge them once they are in dnsmasq master.Checklist:
developmentbranch.