RFC 6731: Improved Recursive DNS Server Selection for Multi-Interfaced Nodes
In plain English — editorial summary, not part of the RFC
A multi-interfaced node is connected to multiple networks, some of which might be utilizing private DNS namespaces. A node commonly receives recursive DNS server configuration information from all connected networks. Some of the recursive DNS servers might have information about namespaces other servers do not have. When a multi-interfaced node needs to utilize DNS, the node has to choose which of the recursive DNS servers to use. This document describes DHCPv4 and DHCPv6 options that can be used to configure nodes with information required to perform informed recursive DNS server selection decisions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6731
- Published
- December 2012
- Authors
- T. Savolainen; J. Kato; T. Lemon
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 29
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 6975Signaling Cryptographic Algorithm Understanding in DNS Security Extensions (DNSSEC)Current
July 2013
- RFC 6418Multiple Interfaces and Provisioning Domains Problem StatementCurrent
November 2011
- RFC 6097Local Mobility Anchor (LMA) Discovery for Proxy Mobile IPv6Current
February 2011
- RFC 5966DNS Transport over TCP - Implementation RequirementsObsoleted
August 2010
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
- RFC 5625DNS Proxy Implementation GuidelinesCurrent
August 2009
- RFC 8005Host Identity Protocol (HIP) Domain Name System (DNS) ExtensionCurrent
October 2016
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?