[GH-ISSUE #1723] Add a configurable do-not-query-list #750

Closed
opened 2026-03-16 00:07:56 +03:00 by kerem · 3 comments
Owner

Originally created by @bluejekyll on GitHub (Jun 6, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1723

Is your feature request related to a problem? Please describe.

We should support both an IP based do-non-query-list as well as a domain name based list. When the IPs will be ignored and not added to the NameserverPools. For names, if they are encountered in any resolution, they will be immediately failed.

Originally created by @bluejekyll on GitHub (Jun 6, 2022). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1723 **Is your feature request related to a problem? Please describe.** We should support both an IP based do-non-query-list as well as a domain name based list. When the IPs will be ignored and not added to the NameserverPools. For names, if they are encountered in any resolution, they will be immediately failed.
Author
Owner

@bluejekyll commented on GitHub (Jan 7, 2024):

See also #13 which is the domain name based option

<!-- gh-comment-id:1879918957 --> @bluejekyll commented on GitHub (Jan 7, 2024): See also #13 which is the domain name based option
Author
Owner

@divergentdave commented on GitHub (Aug 16, 2024):

I'm working on implementing this feature, for IP addresses only. So far I have added filtering of IP addresses when constructing name server pools in hickory-recursor, and plumbed the configuration through to the RecursiveConfig struct in the server. I'm going to work on writing an e2e-tests test for the functionality next, and I'll put a PR up when that's ready.

<!-- gh-comment-id:2294366215 --> @divergentdave commented on GitHub (Aug 16, 2024): I'm working on implementing this feature, for IP addresses only. So far I have added filtering of IP addresses when constructing name server pools in `hickory-recursor`, and plumbed the configuration through to the `RecursiveConfig` struct in the server. I'm going to work on writing an `e2e-tests` test for the functionality next, and I'll put a PR up when that's ready.
Author
Owner

@cpu commented on GitHub (Dec 2, 2025):

I believe this was resolved with https://github.com/hickory-dns/hickory-dns/pull/2369 (for IPs) and the blocklist feature work for domain names. If I'm wrong please add detail on what's left to do & reopen. Thanks!

<!-- gh-comment-id:3602835391 --> @cpu commented on GitHub (Dec 2, 2025): I believe this was resolved with https://github.com/hickory-dns/hickory-dns/pull/2369 (for IPs) and the `blocklist` feature work for domain names. If I'm wrong please add detail on what's left to do & reopen. Thanks!
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#750
No description provided.