[GH-ISSUE #1856] SMIMEA RR support #796

New issue

Closed

opened 2026-03-16 00:16:01 +03:00 by kerem · 3 comments

kerem commented

2026-03-16 00:16:01 +03:00

Owner

Originally created by @HLFH on GitHub (Dec 8, 2022).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1856

Is your feature request related to a problem? Please describe.
SMIMEA RR is not supported.

Describe the solution you'd like
Adding support for SMIMEA RR.

Additional context
https://datatracker.ietf.org/doc/html/rfc8162

Originally created by @HLFH on GitHub (Dec 8, 2022). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/1856 **Is your feature request related to a problem? Please describe.** SMIMEA RR is not supported. **Describe the solution you'd like** Adding support for SMIMEA RR. **Additional context** https://datatracker.ietf.org/doc/html/rfc8162

kerem

2026-03-16 00:16:01 +03:00

closed this issue
added the
enhance

crate:proto
labels

kerem commented

2026-03-16 00:16:17 +03:00

Author

Owner

@djc commented on GitHub (Dec 9, 2022):

Since you've been submitting some issues and PRs, can you talk about what your use case for trust-dns is?

FWIW, I'd be happy to review a PR that adds support for SMIMEA.

@djc commented on GitHub (Dec 9, 2022): Since you've been submitting some issues and PRs, can you talk about what your use case for trust-dns is? FWIW, I'd be happy to review a PR that adds support for SMIMEA.

kerem commented

2026-03-16 00:16:22 +03:00

Author

Owner

@HLFH commented on GitHub (Dec 9, 2022):

I only try to be a power user.
I want to use Trust-DNS as an authoritative DNS server. If that works well, I will use as well the other binaries provided by Trust-DNS (dns cli, recurse, ...).
I was previously an user of PowerDNS for years running it as an authoritative DNS server on two servers (authority/replica), and as a recursive DNS resolver. I am slightly disappointed how PowerDNS handles DNS over TLS and that I have to use a separate package for that (dnsdist).
I like the support that Trust-DNS has for DNS over QUIC and as an user of certbot, I have happily read the last paper that mentioned your project. I am starting to use danectl that works around TLSA, SSHFP, OPENPGPKEY and SMIMEA resource records.

@HLFH commented on GitHub (Dec 9, 2022): I only try to be a power user. I want to use Trust-DNS as an authoritative DNS server. If that works well, I will use as well the other binaries provided by Trust-DNS (dns cli, recurse, ...). I was previously an user of PowerDNS for years running it as an authoritative DNS server on two servers (authority/replica), and as a recursive DNS resolver. I am slightly disappointed how PowerDNS handles DNS over TLS and that I have to use a separate package for that (`dnsdist`). I like the support that Trust-DNS has for DNS over QUIC and as an user of `certbot`, I have happily read the [last paper that mentioned your project](https://letsencrypt.org/2022/12/05/ed-letter-2022.html). I am starting to use [`danectl`](https://github.com/raforg/danectl) that works around TLSA, SSHFP, OPENPGPKEY and SMIMEA resource records.

kerem commented

2026-03-16 00:16:27 +03:00

Author

Owner

@bluejekyll commented on GitHub (Jan 2, 2023):

SMIMEA appears to be the same format as TLSA (and HTTPS) record types. We can add support for it really easily based on that. Once I land #1770 I can quickly add support for this type. It looks like there is some special formatting of the label for the email address that needs to happen based on the RFC, I'm assuming that will be handled by the person creating the record.

@bluejekyll commented on GitHub (Jan 2, 2023): `SMIMEA` appears to be the same format as `TLSA` (and `HTTPS`) record types. We can add support for it really easily based on that. Once I land #1770 I can quickly add support for this type. It looks like there is some special formatting of the label for the email address that needs to happen based on the RFC, I'm assuming that will be handled by the person creating the record.

kerem referenced this issue

2026-03-16 02:20:19 +03:00

[PR #796] [MERGED] update deps 06-2019 #1694