mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #2850] How do you configure blocklists on forwarder zones via Toml Config? #1074
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#1074
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rskntroot on GitHub (Mar 14, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2850
I am trying to get a blocklist running before forwarding requests upstream. I supposed Im going about it all wrong and need help. Appreciate any support.
Have been trying to follow any examples I could find in test_configs.
not only is
zone_type = "External"not valid but im also seeing zones.stores.type =blocklistnot valid too (at least as a part of forwarder).I can load that config when
zones.stores.type=filebut obviously we are going to run into issues wherezones.storescannot be a map...Finally I tried to merge the zone.stores as using type forwarder and the server runs -- but I dont get any blocklist features.
and as expected, blocklisted names are not denied.
@djc commented on GitHub (Mar 14, 2025):
Which version are you using?
@rskntroot commented on GitHub (Mar 14, 2025):
from
cargo install hickory-dns@djc commented on GitHub (Mar 14, 2025):
Ah, sorry, missed that. The test configs you're looking at are from the main branch though, right? There's substantial delta between those. You'll want to try the latest 0.25.0-alpha.5, or even better, compile from main.
(We're on the cusp of releasing 0.25.0, see #2206.)
@rskntroot commented on GitHub (Mar 14, 2025):
I'll give it a shot when I get some time, thank you.
@rskntroot commented on GitHub (Mar 15, 2025):
im now running a build of main branch with default features and have tested a couple different configurations
tl;dr from what I can tell the expected use case isn't currently support as
Externalzones' dont supportblockliststores. see below for expected implementation patterns.my goal is to run a blocklist in front of a forwarder
-- the examples show blocklists in-front of a recursor, but it looks like those haven't been merged in yet, so no worries.
multiple
zones.storeswherezones.type="External"this throws:
blocklists in
forwardzones.storeswherezones.type="External"@marcus0x62 commented on GitHub (Mar 28, 2025):
Hi @rskntroot, the config you posted earlier:
works for me with hickory built from the main branch. How are you building the hickory-dns binary? Based on the error you've posted, I suspect the blocklist feature is not being enabled.
You'll need to build with --features=blocklist in order to use the blocklist authority:
cargo build --bin hickory-dns --features=blocklist --release@rskntroot commented on GitHub (Mar 31, 2025):
can confirm, building with
--features=blocklistdid it. thank you!