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 (RA) options (called "DNS RA options") to allow IPv6 routers to advertise a list of DNS Recursive Server Addresses and a DNS Search List to IPv6 hosts. This document, which obsoletes RFC 6106, defines a higher default value of the lifetime of the DNS RA options to reduce the likelihood of expiry of the options on links with a relatively high rate of packet loss.
Document record
- Document ID
- RFC8106
- Published
- March 2017
- Authors
- J. Jeong; S. Park; L. Beloeil; S. Madanapalli
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
- Obsoletes:
- RFC 6106
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 →
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 8105Transmission of IPv6 Packets over Digital Enhanced Cordless Telecommunications (DECT) Ultra Low Energy (ULE)Current
May 2017
- RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent
March 2017
- RFC 8115DHCPv6 Option for IPv4-Embedded Multicast and Unicast IPv6 PrefixesCurrent
March 2017
- RFC 8096The IPv6-Specific MIB Modules Are ObsoleteCurrent
April 2017
- RFC 8117Current Hostname Practice Considered HarmfulCurrent
March 2017
- RFC 8094DNS over Datagram Transport Layer Security (DTLS)Current
February 2017
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?