[GH-ISSUE #1694] Who uses Trust-DNS authoritative server in production? #737

Closed
opened 2026-03-16 00:04:28 +03:00 by kerem · 9 comments
Owner

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.

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.
kerem 2026-03-16 00:04:28 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

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

<!-- gh-comment-id:1099083263 --> @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.
Author
Owner

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

<!-- gh-comment-id:1099142638 --> @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](https://github.com/BiznetGIO/digs) app. Already depends on one of trust DNS component for over a year. I have asked about this idea [here](https://discord.com/channels/590067103822774272/590067103822774274/957209620756201512), and Benjamin gives a green signal.
Author
Owner

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

<!-- gh-comment-id:1099164742 --> @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...)
Author
Owner

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

<!-- gh-comment-id:1099171876 --> @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.
Author
Owner

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

<!-- gh-comment-id:1099326244 --> @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.
Author
Owner

@peterthejohnston commented on GitHub (Apr 14, 2022):

@peterthejohnston are you willing/able to go on the record about how you use trust-dns?

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.

<!-- gh-comment-id:1099367366 --> @peterthejohnston commented on GitHub (Apr 14, 2022): > @peterthejohnston are you willing/able to go on the record about how you use trust-dns? Sure, happy to. We use Trust-DNS's [resolver](https://crates.io/crates/trust-dns-resolver) crate (with some Fuchsia-specific wrapper/integration code) as the production system DNS resolver for Fuchsia (see [here](https://cs.opensource.google/fuchsia/fuchsia/+/main:src/connectivity/network/dns/) 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.
Author
Owner

@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 ;)

<!-- gh-comment-id:1102793793 --> @dns2utf8 commented on GitHub (Apr 19, 2022): I use it as a network debugging tool for myself and my clients: [dynamic.estada.ch](https://dynamic.estada.ch/) It is publicly accessible. However, there is no SLA yet, as noone is paying me yet ;)
Author
Owner

@azzamsa commented on GitHub (Apr 19, 2022):

Thanks everyone!
Now I have clear view about the usage of Trust-DNS components in the wild.

<!-- gh-comment-id:1103142027 --> @azzamsa commented on GitHub (Apr 19, 2022): Thanks everyone! Now I have clear view about the usage of Trust-DNS components in the wild.
Author
Owner

@azzamsa commented on GitHub (Jul 20, 2022):

Closing as this issue is not actionable. Should be in "discussion" section.

<!-- gh-comment-id:1189833045 --> @azzamsa commented on GitHub (Jul 20, 2022): Closing as this issue is not actionable. Should be in "discussion" section.
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#737
No description provided.