Skip to main content

Improved DNS Server Selection for Multi-Homed Nodes

Document Type Replaced Internet-Draft (individual)
Expired & archived
Authors Teemu Savolainen , Jun-ya Kato
Last updated 2011-01-14 (Latest revision 2011-01-07)
Replaces draft-savolainen-6man-fqdn-based-if-selection
Replaced by draft-ietf-mif-dns-server-selection
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-mif-dns-server-selection
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


A multi-homed node can be connected to multiple networks that may utilize different DNS namespaces. The node often receives DNS server configuration information from all connected networks. Some of the DNS servers may have information about namespaces other servers do not have. When the multi-homed node needs to utilize DNS, it has to choose which of the servers to contact to. This document describes a policy based method for helping on selection of DNS server for both forward and reverse DNS lookup procedures with help of DNS suffix and IPv6 prefix information received via DHCPv6.


Teemu Savolainen
Jun-ya Kato

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