RFC 2065:Domain Name System Security Extensions
RFC-Ref

private key


Click on the red underlined text to get to the source

... DNS cryptographically generated digital signatures. Commonly, there will be a single private key that signs for an entire zone. If a security aware resolver reliably learns the public key ...
... signed data read from that zone, that it was properly authorized and is reasonably current. The expected implementation is for the zone private key to be kept off-line and used to re-sign all of the records in the zone periodically. ...
... SIG resource record is signed by other than the zone private key. One is for support of dynamic update where an entity ...
... The private keys used in transaction and request security belongs to ...
... Because requests and replies are highly variable, message authentication SIGs can not be pre-calculated. Thus it will be necessary to keep the private key on-line, for example in software or in a directly connected piece of hardware ...


... zone key as a non-zone key will usually require that the corresponding private key be kept on line and thereby become more vulnerable. ...


... cryptographic techniques and the signer's private key. The signer is frequently the owner of the zone from which the RR ...
... 1321, "|" is concatenation, "e" is the private key exponent of the signer, and "n" is the modulus of the signer ...


... It is recommended that zone private keys and the zone file master copy be kept and used in off-line non-network ...
... Non-zone private keys, such as host or user keys, generally have to be kept on line to be used for real-time ...


... NXT RRs in zone files and (2) ability, given a zone file and private key, to add appropriate SIG and NXT ...



Google
Web
RFC-Ref