mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 11:15:54 +03:00
[GH-ISSUE #3084] What should Hickory DNS's default be for trust_negative_responses? #1129
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#1129
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 @iximeow on GitHub (Jun 23, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3084
in 2022
NameServerConfiggot aNameServerConfig::new()to create a config with some defaults, withtrust_nx_responses: true. at the same time, the doc comment for trust_negative_responses refers to an older default offalsefrom when it was serializable withserde. and then more recently, #3052 set the defaults in the builders back totrust_negative_responses: false.it seems like
trust_negative_responses: truegenerally seems like a reasonable default, but whatever it is the doc comment should be aligned with the builders!@djc commented on GitHub (Jun 24, 2025):
Submitted a proposed fix in #3085.