RFC 3225: Indicating Resolver Support of DNSSEC

In order to deploy DNSSEC (Domain Name System Security Extensions) operationally, DNSSEC aware servers should only perform automatic inclusion of DNSSEC RRs…

Read RFC 3225 on the RFC Editor

Outgoing relationships (5 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 1035: Domain names - implementation and specification
Informative reference — RFC 1034: Domain names - concepts and facilities
Informative reference — RFC 2535: Domain Name System Security Extensions
Informative reference — RFC 2671: Extension Mechanisms for DNS (EDNS0)

Incoming relationships (13 related RFCs)

Updated by, Normatively referenced by — RFC 4033: DNS Security Introduction and Requirements
Updated by — RFC 4034: Resource Records for the DNS Security Extensions
Updated by — RFC 4035: Protocol Modifications for the DNS Security Extensions
Normatively referenced by — RFC 6891: Extension Mechanisms for DNS (EDNS(0))
Normatively referenced by — RFC 9460: Service Binding and Parameter Specification via the DNS (SVCB and HTTPS Resource Records)
Normatively referenced by — RFC 6840: Clarifications and Implementation Notes for DNS Security (DNSSEC)
Normatively referenced by — RFC 3655: Redefinition of DNS Authenticated Data (AD) bit
Normatively referenced by — RFC 3658: Delegation Signer (DS) Resource Record (RR)
Normatively referenced by — RFC 8906: A Common Operational Problem in DNS Servers: Failure to Communicate
Normatively referenced by — RFC 9824: Compact Denial of Existence in DNSSEC
Informatively referenced by — RFC 3755: Legacy Resolver Compatibility for Delegation Signer (DS)
Informatively referenced by — RFC 4956: DNS Security (DNSSEC) Opt-In
Informatively referenced by — RFC 8904: DNS Whitelist (DNSWL) Email Authentication Method Extension