-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support for resolving CAA records #19239
Labels
dns
Issues and PRs related to the dns subsystem.
Comments
Not sure whether c-ares supports CAA, probably something for #14713. |
It doesn't. |
8 tasks
Continues in #14713. |
lxdicted
added a commit
to lxdicted/node
that referenced
this issue
Oct 2, 2020
This adds support for DNS Certification Authority Authorization (RFC 6844) to nodejs. This closes nodejs#19239 and possibly affects nodejs#14713.
aduh95
pushed a commit
that referenced
this issue
Oct 16, 2020
This adds support for DNS Certification Authority Authorization (RFC 8659) to Node.js. PR-URL: #35466 Fixes: #19239 Refs: #14713 Reviewed-By: Anna Henningsen <[email protected]>
targos
pushed a commit
that referenced
this issue
May 1, 2021
This adds support for DNS Certification Authority Authorization (RFC 8659) to Node.js. PR-URL: #35466 Fixes: #19239 Refs: #14713 Reviewed-By: Anna Henningsen <[email protected]>
Has this been implemented in the Must CAA checks must be done in a side channel / layered in a client library? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This type of record is defined by rfc6844.
The text was updated successfully, but these errors were encountered: