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

New issue

Closed

opened 2026-03-15 22:00:34 +03:00 by kerem · 3 comments

kerem commented

2026-03-15 22:00:34 +03:00

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-15 22:00:34 +03:00

closed this issue
added the
enhance
label

kerem commented

2026-03-15 22:00:50 +03:00

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.

@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.

kerem commented

2026-03-15 22:00:55 +03:00

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.

@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.

kerem commented

2026-03-15 22:01:00 +03:00

Author

Owner

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

#163 should be enough for this.

@bluejekyll commented on GitHub (Jul 4, 2017): #163 should be enough for this.

kerem referenced this issue

2026-03-16 02:02:41 +03:00

[PR #328] [MERGED] NameUsage patterns #1368