-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
CAA DNS RR #1732
CAA DNS RR #1732
Conversation
I open issue 14066 on Redmine for that PR |
lib/resolv.rb
Outdated
# Creates a new CAA for +flag+, +tag+ and +value+. | ||
|
||
def initialize(flag, tag, value) | ||
@flag, @tag, @value = flag, tag, value |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Elsewhere in this file assignment to instance variables is done using one line per assignment. Perhaps you want to align with the existing code-style?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed :)
Introduce CAA RR DNS record on `Resolv`, defined in [RFC 6844](https://tools.ietf.org/html/rfc6844). Changes on the way `Resource::decode_rdata` works because CAA needs to know the overall RR length, which was previously swallowed.
Thanks for this PR, I was also looking for this and so am currently using the patch. Is there anything blocking this from being upstreamed into ruby? CAA is a fairly standard and widely adopted DNS record type now. |
I rebased this patch and filed a PR in the upstream repository. ruby/resolv#48 |
Thanks @hanazuki ! |
Introduce CAA RR DNS record on
Resolv
, defined in RFC 6844.Changes on the way
Resource::decode_rdata
works because CAA needs to know theoverall RR length, which was previously swallowed.