[GH-ISSUE #47] [Server] Feature request: Allow custom backends to be used for Authorities/Catalogs #31

Closed
opened 2026-03-07 22:18:10 +03:00 by kerem · 3 comments
Owner

Originally created by @rushmorem on GitHub (Oct 5, 2016).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/47

As the title, says. Split out the low level functions into a nice DNS library and then build the server and client crates on top of that library. See https://github.com/bluejekyll/trust-dns/issues/43#issuecomment-251733340 and the comments that follow that one for details.

Originally created by @rushmorem on GitHub (Oct 5, 2016). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/47 As the title, says. Split out the low level functions into a nice DNS library and then build the server and client crates on top of that library. See https://github.com/bluejekyll/trust-dns/issues/43#issuecomment-251733340 and the comments that follow that one for details.
kerem 2026-03-07 22:18:10 +03:00
  • closed this issue
  • added the
    enhance
    label
Author
Owner

@bluejekyll commented on GitHub (Oct 6, 2016):

More specifically, I think we want generic traits for many of the core structures which would allow arbitrary implementations to work in various contexts.

Example: Server<C: Catalog>::new(C), where C could be some arbitrary backing datastore.

<!-- gh-comment-id:251861198 --> @bluejekyll commented on GitHub (Oct 6, 2016): More specifically, I think we want generic traits for many of the core structures which would allow arbitrary implementations to work in various contexts. Example: Server<C: Catalog>::new(C), where C could be some arbitrary backing datastore.
Author
Owner

@bluejekyll commented on GitHub (Oct 20, 2016):

I changed the title, I think it's more accurate to what this request is about, as it was written it sounded like a dup of the library splitup.

<!-- gh-comment-id:255023530 --> @bluejekyll commented on GitHub (Oct 20, 2016): I changed the title, I think it's more accurate to what this request is about, as it was written it sounded like a dup of the library splitup.
Author
Owner

@bluejekyll commented on GitHub (Jul 4, 2017):

#163 should be enough for this.

<!-- gh-comment-id:312935536 --> @bluejekyll commented on GitHub (Jul 4, 2017): #163 should be enough for this.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/hickory-dns#31
No description provided.