Dynamic Host Configuration Protocol (DHCP) Domain Search Option
RFC 3397

Document Type RFC - Proposed Standard (November 2002; No errata)
Was draft-aboba-dhc-domsearch (individual)
Last updated 2012-02-26
Stream IETF
Formats plain text pdf htmlized bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 3397 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           B. Aboba
Request for Comments: 3397                                     Microsoft
Category: Standards Track                                    S. Cheshire
                                                    Apple Computer, Inc.
                                                           November 2002

    Dynamic Host Configuration Protocol (DHCP) Domain Search Option

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2002).  All Rights Reserved.

Abstract

   This document defines a new Dynamic Host Configuration Protocol
   (DHCP) option which is passed from the DHCP Server to the DHCP Client
   to specify the domain search list used when resolving hostnames using
   DNS.

Table of Contents

   1.  Introduction ................................................  2
        1.1 Terminology ............................................  2
        1.2 Requirements Language ..................................  2
   2.  Domain Search Option Format .................................  2
   3.  Example .....................................................  3
   4.  Security Considerations .....................................  4
   5.  Normative References ........................................  5
   6.  Informative References ......................................  5
   7.  IANA Considerations .........................................  6
   8.  Acknowledgments .............................................  6
   9.  Intellectual Property Statement .............................  6
   10. Authors' Addresses ..........................................  7
   11. Full Copyright Statement ....................................  8

Aboba & Cheshire            Standards Track                     [Page 1]
RFC 3397               DHCP Domain Search Option           November 2002

1.  Introduction

   The Dynamic Host Configuration Protocol (DHCP) [RFC2131] provides a
   mechanism for host configuration.  [RFC2132] and [RFC2937] allow DHCP
   servers to pass name service configuration information to DHCP
   clients.  In some circumstances, it is useful for the DHCP client to
   be configured with the domain search list.  This document defines a
   new DHCP option which is passed from the DHCP Server to the DHCP
   Client to specify the domain search list used when resolving
   hostnames with DNS.  This option applies only to DNS and does not
   apply to other name resolution mechanisms.

1.1.  Terminology

   This document uses the following terms:

   DHCP client
         A DHCP client or "client" is an Internet host using DHCP to
         obtain configuration parameters such as a network address.

   DHCP server
         A DHCP server or "server" is an Internet host that returns
         configuration parameters to DHCP clients.

1.2.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in "Key words for use in
   RFCs to Indicate Requirement Levels" [RFC2119].

2.  Domain Search Option Format

   The code for this option is 119.

    0                   1                   2                   3
    0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |     119       |     Len       |         Searchstring...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
   |                     Searchstring...
   +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

   In the above diagram, Searchstring is a string specifying the
   searchlist.  If the length of the searchlist exceeds the maximum
   permissible within a single option (255 octets), then multiple
   options MAY be used, as described in "Encoding Long Options in the
   Dynamic Host Configuration Protocol (DHCPv4)" [RFC3396].

Aboba & Cheshire            Standards Track                     [Page 2]
RFC 3397               DHCP Domain Search Option           November 2002

   To enable the searchlist to be encoded compactly, searchstrings in
   the searchlist MUST be concatenated and encoded using the technique
   described in section 4.1.4 of "Domain Names - Implementation And
   Specification" [RFC1035].  In this scheme, an entire domain name or a
   list of labels at the end of a domain name is replaced with a pointer
   to a prior occurrence of the same name.  Despite its complexity, this
   technique is valuable since the space available for encoding DHCP
Show full document text