datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Improved Recursive DNS Server Selection for Multi-Interfaced Nodes
draft-ietf-mif-dns-server-selection-12

RFC
Document Stream: IETF
Last updated: 2012-08-02
Replaces: draft-savolainen-mif-dns-server-selection
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: Submitted to IESG for Publication (mif)
Document shepherd:Hui Deng
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6731
IANA Action State: RFC-Ed-Ack 
On agenda of 2012-06-21 IESG telechat
Responsible AD: Ralph Droms
IESG Note: Hui Deng (denghui02@hotmail.com ) is the document shepherd.
Send notices to: mif-chairs@tools.ietf.org, draft-ietf-mif-dns-server-selection@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-mif-dns-server-selection.

Abstract:
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]

Authors:
Teemu Savolainen <teemu.savolainen@nokia.com>
Jun-ya Kato <kato@syce.net>
Ted Lemon <ted.lemon@nominum.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)