mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-25 03:05:51 +03:00
[GH-ISSUE #1694] Who uses Trust-DNS authoritative server in production? #737
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#737
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 @azzamsa on GitHub (Apr 14, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1694
Hi.
IMHO, it is better to have a list of individual or company that uses Trust-DNS authoritative server in the production environment.
@djc commented on GitHub (Apr 14, 2022):
Why do you want to know, and what do you want to know exactly? This is a fairly vague question. Trust-DNS is a big project, so different parts of the project might have different levels of maturity/popularity.
@azzamsa commented on GitHub (Apr 14, 2022):
Hi, I think I am missing the "authoritative server" word.
For the context. We have been using Knot DNS authoritative server for over 2 years in production. But every one or two week we always got the same memory issue. We have reported the issue upstream. They responded and helped us well. But the issue persist even on the latest revision.
We would like to try Trust DNS authoritative server. And see if it meets all our requirements. ( I think it will be). But we will try it first. Currently, our digs app. Already depends on one of trust DNS component for over a year.
I have asked about this idea here, and Benjamin gives a green signal.
@djc commented on GitHub (Apr 14, 2022):
Fair enough. We use trust-dns for our authoritative DNS server at instantdomains.com. We don't exactly use everything that the trust-dns-server crate provides, though, our use case is maybe odd because we have a large dynamic set of authorities.
@peterthejohnston are you willing/able to go on the record about how you use trust-dns? @jeff-hiner, @edevil same? (Even if it's not about the authoritative name server...)
@Darkspirit commented on GitHub (Apr 14, 2022):
If I can trust my calendar, I finally removed PowerDNS on 2019-03-02 and use Trust-DNS as my only authoritative dns server since then (zones with DNSSEC P-384 via ring, CAA validationmethods=dns-01).
I use an own incomplete/dirty written Rust app for ACME via DNS (Dynamic update via Trust-DNS client #556, Reqwest, Rustls) that also sets TLSA records for Web, Postfix, Prosody and reloads them.
I just noticed that I last updated my Trust-DNS server on 2021-03-02 (Edit: lol, same date as above, but different year) as I haven't encountered any bugs since then, so I'm likely still on 0.20.0: https://github.com/bluejekyll/trust-dns/blob/main/CHANGELOG.md#0200
I'll update it later.
If I remember correctly, Trust-DNS is also used by Fuchsia, Google's Android successor.
@jeff-hiner commented on GitHub (Apr 14, 2022):
Right now my team is prototyping an implementation of trust-dns-server tied to trust-dns-resolver as a proxy. I don't believe we're using it in production for authoritative name servers.
@peterthejohnston commented on GitHub (Apr 14, 2022):
Sure, happy to. We use Trust-DNS's resolver crate (with some Fuchsia-specific wrapper/integration code) as the production system DNS resolver for Fuchsia (see here for the code). Last year Fuchsia was launched on the first-gen Nest Hub, so it's been used in production since then.
We don't use the Trust-DNS server crate, though, which I guess was the original question here.
@dns2utf8 commented on GitHub (Apr 19, 2022):
I use it as a network debugging tool for myself and my clients: dynamic.estada.ch
It is publicly accessible. However, there is no SLA yet, as noone is paying me yet ;)
@azzamsa commented on GitHub (Apr 19, 2022):
Thanks everyone!
Now I have clear view about the usage of Trust-DNS components in the wild.
@azzamsa commented on GitHub (Jul 20, 2022):
Closing as this issue is not actionable. Should be in "discussion" section.