mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[PR #2161] [MERGED] Chained authority implementation #2845
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#2845
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?
📋 Pull Request Information
Original PR: https://github.com/hickory-dns/hickory-dns/pull/2161
Author: @marcus0x62
Created: 2/29/2024
Status: ✅ Merged
Merged: 9/27/2024
Merged by: @marcus0x62
Base:
main← Head:chained_authority📝 Commits (3)
6cf8ac9Server and catalog changes to support chained authorities4ab00d2Chained authorityb3076d7Tests for the chained authority📊 Changes
18 files changed (+781 additions, -229 deletions)
View changed files
📝
bin/src/hickory-dns.rs(+134 -110)📝
crates/server/src/authority/authority.rs(+35 -0)📝
crates/server/src/authority/authority_object.rs(+68 -0)📝
crates/server/src/authority/catalog.rs(+104 -72)📝
crates/server/src/config/mod.rs(+2 -2)📝
crates/server/src/store/config.rs(+18 -0)📝
crates/server/src/store/mod.rs(+1 -0)📝
crates/server/tests/integration/config_tests.rs(+34 -23)📝
tests/integration-tests/Cargo.toml(+1 -0)📝
tests/integration-tests/tests/integration/catalog_tests.rs(+10 -10)➕
tests/integration-tests/tests/integration/chained_authority_tests.rs(+361 -0)📝
tests/integration-tests/tests/integration/client_future_tests.rs(+3 -3)📝
tests/integration-tests/tests/integration/client_tests.rs(+2 -2)📝
tests/integration-tests/tests/integration/dnssec_client_handle_tests.rs(+1 -1)📝
tests/integration-tests/tests/integration/lookup_tests.rs(+4 -4)📝
tests/integration-tests/tests/integration/main.rs(+1 -0)📝
tests/integration-tests/tests/integration/server_future_tests.rs(+1 -1)📝
tests/integration-tests/tests/integration/truncation_tests.rs(+1 -1)📄 Description
This is a standalone PR for the chained authority feature discussed in PR #2113
It implements the cases discussed earlier, including the consult case where an authority can modify an answer -- positive or negative -- from a previous authority, except when LookupControlFlow::Break is returned, which will result in an immediate response being sent.
While working on this, I found that the LookupControlFlow logic in the catalog was spread out and duplicated across more of the code base than it really needed to be, so there's a separate commit here to clean that up. Hopefully it makes reviewing the core changes a bit easier.
closes: #2113
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.