RFC 3596: DNS Extensions to Support IP Version 6
In plain English — editorial summary, not part of the RFC
This document defines the changes that need to be made to the Domain Name System (DNS) to support hosts running IP version 6 (IPv6). The changes include a resource record type to store an IPv6 address, a domain to support lookups based on an IPv6 address, and updated definitions of existing query types that return Internet addresses as part of additional section processing. The extensions are designed to be compatible with existing applications and, in particular, DNS implementations themselves. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3596
- Published
- October 2003
- Authors
- S. Thomson; C. Huitema; V. Ksinant; M. Souissi
- Status
- INTERNET STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 8
- Also known as
- STD88
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 1886 (1995)
- RFC 3152 (2001)
- RFC 3596 (2003)
Read the full history of DNS Extensions to Support IP Version 6 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 3901DNS IPv6 Transport Operational GuidelinesObsoleted
September 2004
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3646DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)Current
December 2003
- RFC 3658Delegation Signer (DS) Resource Record (RR)Obsoleted
December 2003
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
- RFC 3110RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)Updated
May 2001
- RFC 2931DNS Request and Transaction Signatures ( SIG(0)s )Current
September 2000
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?