RFC 2845:Secret Key Transaction Authentication for...
RFC-Ref

transaction


Click on the red underlined text to get to the source

... [RFC2535] provides public key transaction signatures to support this, but such signatures ...
... point-to-point authentication and integrity checking for transactions. ...
... signatures but with [RFC2535] they, like transaction signatures, require computationally expensive public key cryptography ...
... authenticate DNS update requests as well as transaction responses, providing a lightweight alternative to the protocol described by [RFC2137 ...
... does not protect glue records and unsigned records unless SIG(0) (transaction signature) is used. ...
... 1.6. A server acting as an indirect caching resolver -- a "forwarder" in common usage -- might use transaction-based authentication when communicating with its small number of preconfigured "upstream ...


... RRs are dynamically computed to cover a particular DNS transaction and are not DNS RRs ...
... TYPE TSIG (250: Transaction SIGnature) ...


... nonempty additional data section. Clients SHOULD only attempt signed transactions with servers who are known to support TSIG and share some secret key ...
... destination or the next forwarder. If no transaction security is available to the destination ...


... host. For this reason, a host that implements transaction-based authentication should probably be configured with a "stub resolver" and a local ...



Google
Web
RFC-Ref