mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #2357] Build arguments for hickory-dns recursor type #969
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#969
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 @git001 on GitHub (Aug 14, 2024).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/2357
I used the following file to run my own recursive resolver and got the error that
type = "recursor"isn't known.https://github.com/hickory-dns/hickory-dns/blob/main/tests/test-data/test_configs/example_recursor.toml#L36-L40
After some checks I have found the right build arguments and want to share the knowledge with the
hickory-dnscommunity.Now my question:
What's the best place to add this information to the users when they want to use
hickory-dnsas recursive resolver.With that option can I run my own resolver server with
hickory-dns😄@bluejekyll commented on GitHub (Mar 2, 2025):
Thanks, we should add this to our docs.