RFC 6106: IPv6 Router Advertisement Options for DNS Configuration
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8106.
Current document in this lineage: RFC 8106 — IPv6 Router Advertisement Options for DNS Configuration
In plain English — editorial summary, not part of the RFC
This document specifies IPv6 Router Advertisement options to allow IPv6 routers to advertise a list of DNS recursive server addresses and a DNS Search List to IPv6 hosts. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6106
- Published
- November 2010
- Authors
- J. Jeong; S. Park; L. Beloeil; S. Madanapalli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 5006 (2007)
- RFC 6106 (2010)
- RFC 8106 (2017) ✓
Read the full history of IPv6 Router Advertisement Options for DNS Configuration →
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 6059Simple Procedures for Detecting Network Attachment in IPv6Current
November 2010
- RFC 4944Transmission of IPv6 Packets over IEEE 802.15.4 NetworksUpdated
September 2007
- RFC 6098Generic Notification Message for Mobile IPv4Current
April 2012
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 6089Flow Bindings in Mobile IPv6 and Network Mobility (NEMO) Basic SupportCurrent
January 2011
- RFC 6088Traffic Selectors for Flow BindingsCurrent
January 2011
- RFC 6079HIP BONE: Host Identity Protocol (HIP) Based Overlay Networking Environment (BONE)Current
January 2011
- RFC 6078Host Identity Protocol (HIP) Immediate Carriage and Conveyance of Upper-Layer Protocol Signaling (HICCUPS)Current
January 2011
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?