Net::DNS::RR::SIG(3)
π Net::DNS::RR::SIG β DNS SIG resource record π
okay bestie, welcome to the glow-up era of the SIG RR π
this page lives in the User Contributed Perl Documentation section, which is basically the group chat of the Perl world β and yes, Net::DNS::RR::SIG is the main character here.
β¨ SYNOPSIS β¨
use Net::DNS;
$rr = Net::DNS::RR->new('name SIG typecovered algorithm labels
orgttl sigexpiration siginception
keytag signame signature');
use Net::DNS::SEC;
$sigrr = Net::DNS::RR::SIG->create(
$string, $keypath,
sigval => 10 # minutes
);
$sigrr->verify( $string, $keyrr ) || die $sigrr->vrfyerrstr;
$sigrr->verify( $packet, $keyrr ) || die $sigrr->vrfyerrstr;
no cap, that's the whole vibe right there π«Ά
πΈ DESCRIPTION πΈ
so this is the class for DNS digital signature (SIG) resource records. iconic. π«
on top of all the regular methods you inherit from Net::DNS::RR, this class is carrying two extra things: a method that signs packets and scalar data strings using private keys (create), and a method for verifying signatures. it's giving "we do both" energy, honestly π
real talk though β the SIG RR is an implementation of RFC2931. if you were looking for RFC4034, that's Net::DNS::RR::RRSIG, a whole other girl. don't mix them up bestie π
π METHODS π
the available methods are the ones inherited from the base class, plus the type-specific methods defined in this package. so you get the whole family π
β οΈ use of undocumented package features or direct access to internal data structures is discouraged and could result in program termination or other unpredictable behaviour. like, don't go digging through her private messages, it's not cute π
π algorithm
$algorithm = $rr->algorithm;
the algorithm number field identifies the cryptographic algorithm used to create the signature. lowkey the fingerprint of the whole thing π
algorithm() may also be invoked as a class method or simple function to perform mnemonic and numeric code translation β so it pulls double duty, we love a multi-hyphenate β¨
π sigexpiration and siginception times
π sigex sigin sigval
$expiration = $rr->sigexpiration;
$expiration = $rr->sigexpiration( $value );
$inception = $rr->siginception;
$inception = $rr->siginception( $value );
the signature expiration and inception fields specify a validity time interval for the signature. basically: when the vibe starts and when it expires π°οΈ
the value may be specified by a string with format 'yyyymmddhhmmss' or a Perl time() value.
return values are dual-valued, providing either a string value or numerical Perl time() value. she contains multitudes, fr fr π
π keytag
$keytag = $rr->keytag;
$rr->keytag( $keytag );
the keytag field contains the key tag value of the KEY RR that validates this signature. it's the little ID badge that says "this key, right here" πͺͺ
π signame
$signame = $rr->signame;
$rr->signame( $signame );
the signer name field value identifies the owner name of the KEY RR that a validator is supposed to use to validate this signature. iykyk β it's pointing at the right person ππ
π signature
π sig
$sig = $rr->sig;
$rr->sig( $sig );
the Signature field contains the cryptographic signature that covers the SIG RDATA (excluding the Signature field) and the subject data. yes, it covers everything except itself. she's humble like that πΈ
π sigbin
$sigbin = $rr->sigbin;
$rr->sigbin( $sigbin );
binary representation of the cryptographic signature. raw bytes, no makeup, still stunning πβ¨
π create
create a signature over scalar data.
use Net::DNS::SEC;
$keypath = '/home/olaf/keys/Kbla.foo.+001+60114.private';
$sigrr = Net::DNS::RR::SIG->create( $data, $keypath );
$sigrr = Net::DNS::RR::SIG->create(
$data, $keypath,
sigval => 10
);
$sigrr->print;
# Alternatively use Net::DNS::SEC::Private
$private = Net::DNS::SEC::Private->new($keypath);
$sigrr= Net::DNS::RR::SIG->create( $data, $private );
create() is an alternative constructor for a SIG RR object. your other entry point, bestie πͺβ¨
this method returns a SIG with the signature over the data made with the private key stored in the key file.
- the first argument is a scalar that contains the data to be signed.
- the second argument is a string which specifies the path to a file containing the private key as generated using
dnssec-keygen, a program that comes with the ISC BIND distribution.
the optional remaining arguments consist of ( name => value ) pairs as follows:
sigin => 20251201010101, # signature inception
sigex => 20251201011101, # signature expiration
sigval => 10, # validity window (minutes)
the sigin and sigex values may be specified as Perl time values or as a string with the format 'yyyymmddhhmmss'. the default for sigin is the time of signing. β±οΈ
the sigval argument specifies the signature validity window in minutes ( sigex = sigin + sigval ).
by default the signature is valid for 10 minutes. ten minutes!! so don't be late to the function π
π verify
$verify = $sigrr->verify( $data, $keyrr );
$verify = $sigrr->verify( $data, [$keyrr, $keyrr2, $keyrr3] );
the verify() method performs SIG0 verification of the specified data against the signature contained in the $sigrr object itself using the public key in $keyrr. it's the vibe check πβ¨
if a reference to a Net::DNS::Packet is supplied, the method performs a SIG0 verification on the packet data.
the second argument can either be a Net::DNS::RR::KEY object or a reference to an array of such objects. verification will return successful as soon as one of the keys in the array leads to positive validation β first one to say "she's real" wins, squad goals π«Ά
returns false on error and sets $sig->vrfyerrstr
π vrfyerrstr
$sig0 = $packet->sigrr || die 'not signed';
print $sig0->vrfyerrstr unless $sig0->verify( $packet, $keyrr );
$sigrr->verify( $packet, $keyrr ) || die $sigrr->vrfyerrstr;
when it fails, it tells you why. communication queen π¬
π KEY GENERATION π
private key files and corresponding public DNSKEY records are most conveniently generated using dnssec-keygen, a program that comes with the ISC BIND distribution. it's basically the key-making fairy godmother π§
dnssec-keygen -a 10 -b 2048 rsa.example.
dnssec-keygen -a 13 -f ksk ecdsa.example.
dnssec-keygen -a 13 ecdsa.example.
π¨ do not change the name of the private key file. thecreatemethod uses the filename as generated bydnssec-keygento determine the keyowner, algorithm, and the keyid (keytag). rename it and the whole thing falls apart, no cap π
π REMARKS π
the code is not optimised for speed. she's not rushing, she's thriving π’β¨
if this code is still around in 2100 (not a leap year) you will need to check for proper handling of times after 28th February. future besties, this one's for you π«‘
π ACKNOWLEDGMENTS π
although their original code may have disappeared following redesign of Net::DNS, Net::DNS::SEC and the OpenSSL API, the following individual contributors deserve to be recognised for their significant influence on the development of the SIG package. legends only, we see you π«Ά
- Andy Vaskys (Network Associates Laboratories) supplied code for RSA.
- T.J. Mather provided support for the DSA algorithm.
- Dick Franks added support for elliptic curve and Edwards curve algorithms.
π COPYRIGHT π
Copyright (c)2001-2005 RIPE NCC, Olaf M. Kolkman
Copyright (c)2007-2008 NLnet Labs, Olaf M. Kolkman
Portions Copyright (c)2014 Dick Franks
All rights reserved.
Package template (c)2009,2012 O.M.Kolkman and R.W.Franks.
π LICENSE π
Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the original copyright notices appear in all copies and that both copyright notice and this permission notice appear in supporting documentation, and that the name of the author not be used in advertising or publicity pertaining to distribution of the software without specific prior written permission.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
π¦ SEE ALSO π¦
perlNet::DNSNet::DNS::RRNet::DNS::SEC- RFC2535(4) <https://iana.org/go/rfc2535#section-4>
- RFC2936 <https://iana.org/go/rfc2936>
- RFC2931 <https://iana.org/go/rfc2931>
- RFC3110 <https://iana.org/go/rfc3110>
- RFC4034 <https://iana.org/go/rfc4034>
- Algorithm Numbers <https://iana.org/assignments/dns-sec-alg-numbers>
- BIND Administrator Reference Manual <https://bind9.readthedocs.io/en/latest/>
and that's the page, bestie!! π go forth and sign your packets π β¨
this has been perl v5.42.0, dated 2026-09-02, signing off from Net::DNS::RR::SIG(3) β periodt π
π¦ where this page comes from
- opensuse-leap 16.0: perl-Net-DNS 1.570.0-bp160.1.1 Β· MIT
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms