RFC 3901: DNS IPv6 Transport Operational Guidelines
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 10001.
Current version: RFC 10001 — Operational Guidelines for DNS Transport in Mixed IPv4/IPv6 Environments
In plain English — editorial summary, not part of the RFC
This memo provides guidelines and Best Current Practice for operating DNS in a world where queries and responses are carried in a mixed environment of IPv4 and IPv6 networks. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.
Document record
- Document ID
- RFC3901
- Published
- September 2004
- Authors
- A. Durand; J. Ihren
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 5
- Also known as
- BCP91
- Obsoleted by:
- RFC 10001
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3596DNS Extensions to Support IP Version 6Current
October 2003
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 6168Requirements for Management of Name Servers for the DNSCurrent
May 2011
- RFC 8552Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute LeavesCurrent
March 2019
- RFC 8553DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node NamesCurrent
March 2019
- RFC 3915Domain Registry Grace Period Mapping for the Extensible Provisioning Protocol (EPP)Current
October 2004
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 3681Delegation of E.F.F.3.IP6.ARPACurrent
January 2004
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?