Zonema...::RRSIG(3pm)
β¨ NAME β¨
Zonemaster::LDNS::RR::RRSIG β the type RRSIG record, bestie π (tucked away in the 3pm manual section, iykyk)
π¦ DESCRIPTION π¦
Okay so real talk: this is a subclass of Zonemaster::LDNS::RR, which means it inherits literally every single method that class has, and then it also has its own extra ones documented down below. So no, you're not missing out on anything, you get the whole bloodline plus more π
It's giving "I contain a DNSSEC signature and I'm not shy about it" energy. Periodt.
π METHODS π
π typecovered()
Hands you back a string with the name of the RR type this signature covers. Like, "who is this signature for?" β it tells you. So helpful of it π«Ά
π algorithm()
Returns the algorithm number. The digits, the vibes, the math. No decoding, just the raw number.
π labels()
Returns the number of labels that was used to calculate the signature. Yes, labels as in DNS labels, not the cute ones on your water bottle π
π origttl()
Returns the original TTL value. The TTL before it got churned up by the zone. The og, if you will πΈ
π expiration()
Returns the expiration time, as a time_t. That's when this signature stops being valid, so mark your calendar bestie π
π inception()
Returns the inception time, as a time_t. When the signature was born β¨
π keytag()
Returns the keytag. Just the keytag. Iconic, brief, no notes π₯
π signer()
Returns the signer name. The name of whoever signed this thing β the main character of this signature's story π
π signature()
Returns the cryptographic signature in binary form. Raw bytes, no makeup, no filter. That's the actual sig right there π
π verify($rrset_ref, $key_ref)
Cryptographically verifies that the signature chillin' in this object matches the given RRset and at least one of the given keys. Let's break it down:
$rrset_refshould be a reference to an array of RR objects$key_refshould be a reference to an array ofZonemaster::LDNS::RR::DNSKEYobjects
And then? This method simply returns a true or false value, depending on the result of the check. That's it. No essay, no drama, just true or false π
π verify_str($rrset_ref, $key_ref)
Takes exactly the same arguments as verify() and does exactly the same thing, except instead of true/false it returns a string describing the result.
- If it worked? The message is literally
"All OK"π - If it didn't? The string describes the reason the verification failed β so you get the why, not just the no π
π verify_time($rrset_ref, $key_ref, $time, $msg)
This is the XS method doing all the actual work behind the previous two. The real MVP, the one in the engine room fr fr.
$rrset_refand$key_refare the same as for the other methods$timeis thetime_tvalue for which the validation should be made β and heads up, for the previous two methods this is set to the current computer time β°$msgshould be a writable scalar, and the string message describing the result will be put in it
The return value from the method is a true/false. So you get a boolean and a note. Overachiever behavior, we love to see it π
π« and that's the whole page bestie π«
Okay so this was Zonemaster::LDNS::RR::RRSIG from perl v5.42.3, dated 2026-08-19, straight out of the User Contributed Perl Documentation. Go forth and verify your RRsets, you absolute legend π§πΈπ
π¦ where this page comes from
- ubuntu stonking: libzonemaster-ldns-perl 5.0.2+ds-2build1 Β· BSD-2-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms