[GH-ISSUE #234] [Server] Please add support for CAA records #406

New issue

Closed

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

kerem commented

2026-03-15 22:21:51 +03:00

Owner

Originally created by @Darkspirit on GitHub (Oct 15, 2017).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/234

github.com/bluejekyll/trust-dns@f4d8ae1f51/proto/src/rr/record_type.rs (L43)

I would like to set ones here: http://dnsviz.net/d/dev.terrax.net/dnssec/ (trust-dns)
for https://github.com/TerraX-net/terrax

Originally created by @Darkspirit on GitHub (Oct 15, 2017). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/234 https://github.com/bluejekyll/trust-dns/blob/f4d8ae1f512796b8ac1ea47f8b27e6849c03b407/proto/src/rr/record_type.rs#L43 I would like to set ones here: http://dnsviz.net/d/dev.terrax.net/dnssec/ (trust-dns) for https://github.com/TerraX-net/terrax

kerem

2026-03-15 22:21:51 +03:00

closed this issue
added the
enhance

crate:client

crate:server

crate:proto
labels

kerem commented

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

Author

Owner

@Darkspirit commented on GitHub (Oct 15, 2017):

acme.sh:

[Mon Oct 16 00:31:53 CEST 2017] dev.terrax.net:Verify error:DNS problem: SERVFAIL looking up CAA for dev.terrax.net

https://community.letsencrypt.org/t/caa-servfail-changes/38298/4

We’ve now removed the exceptions list that roland mentioned in his initial message. SERVFAILs for CAA are now treated as failures for all domain names. See https://letsencrypt.org/docs/caa/62 for details on diagnosing and fixing CAA SERVFAIL problems.

I would like to add this to the zone file:

@      CAA 128 issue "letsencrypt.org"
@      CAA 128 iodef "mailto:hostmaster@terrax.net"

128 is the CAA critical bit, 0 is the default.

I will try to switch dev.terrax.net back to powerdns, request a cert and switch back to trust-dns.
Edit: 👍

@Darkspirit commented on GitHub (Oct 15, 2017): acme.sh: > [Mon Oct 16 00:31:53 CEST 2017] dev.terrax.net:Verify error:DNS problem: SERVFAIL looking up CAA for dev.terrax.net https://community.letsencrypt.org/t/caa-servfail-changes/38298/4 > We’ve now removed the exceptions list that roland mentioned in his initial message. SERVFAILs for CAA are now treated as failures for all domain names. See https://letsencrypt.org/docs/caa/62 for details on diagnosing and fixing CAA SERVFAIL problems. I would like to add this to the zone file: ``` @ CAA 128 issue "letsencrypt.org" @ CAA 128 iodef "mailto:hostmaster@terrax.net" ``` 128 is the CAA critical bit, 0 is the default. I will try to switch `dev.terrax.net` back to powerdns, request a cert and switch back to trust-dns. Edit: 👍

kerem commented

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

Author

Owner

@rushmorem commented on GitHub (Oct 21, 2017):

I need this for Let's Encrypt as well.

@rushmorem commented on GitHub (Oct 21, 2017): I need this for Let's Encrypt as well.

kerem commented

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

Author

Owner

@bluejekyll commented on GitHub (Nov 1, 2017):

RFC for this: https://tools.ietf.org/html/rfc6844

I'm looking into this, as this is something I'd very much like to support.

@bluejekyll commented on GitHub (Nov 1, 2017): RFC for this: https://tools.ietf.org/html/rfc6844 I'm looking into this, as this is something I'd very much like to support.

kerem referenced this issue

2026-03-16 02:05:08 +03:00

[PR #406] [CLOSED] Bump serde_derive from 1.0.37 to 1.0.39 #1414