mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 19:25:56 +03:00
[GH-ISSUE #3120] Consider better trait separation for hickory-server InMemoryAuthority and cousins #1137
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#1137
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 @alexrudy on GitHub (Jul 14, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3120
I went to build a DNS server out of hickory components, and found myself implementing my own Authority to provide DNS Authorities backed by a different storage engine (in my case, putting all of my DNS records in a common SQLite DB, rather than storing zone files on disk). Unfortunately, this requires a lot of work, much of it copying implementation from the existing InMemoryAuthority and SqliteAuthority.
It would be great to have the flexibility to provide other storage engines (e.g. ones where an authority might change via some external method during the running of the server). I took a stab at doing this with a trait, and wanted to know if that is a direction y'all have considered for hickory-server.
@djc commented on GitHub (Jul 15, 2025):
In general, I'm a fan of increasing modularity provided this come not at a (substantial) cost in complexity. It's hard to be more definitive without seeing more of the direction you have in mind.
REFUSEDinstead ofNXDOMAINwhen server is not an authority #2004