Reverse DNS in IPv6 for Internet Service Providers
draft-ietf-dnsop-ip6rdns-00

Document Type Active Internet-Draft (dnsop WG)
Last updated 2016-10-31
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Internet Engineering Task Force                                L. Howard
Internet-Draft                                         Time Warner Cable
Intended status: Informational                        September 29, 2014
Expires: April 2, 2015                                                  

           Reverse DNS in IPv6 for Internet Service Providers
                      draft-ietf-dnsop-ip6rdns-00

Abstract

   In IPv4, Internet Service Providers (ISPs) commonly provide IN-
   ADDR.ARPA. information for their customers by prepopulating the zone
   with one PTR record for every available address.  This practice does
   not scale in IPv6.  This document analyzes different approaches for
   ISPs to manage the ip6.arpa zone for IPv6 address space assigned to
   many customers.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 2, 2015.

Copyright Notice

   Copyright (c) 2012 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
 

Howard                   Expires April 2, 2015                  [Page 1]
Internet-Draft        Reverse DNS in IPv6 for ISPs    September 29, 2014

   described in the Simplified BSD License.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1.  Reverse DNS in IPv4  . . . . . . . . . . . . . . . . . . .  3
     1.2.  Reverse DNS Considerations in IPv6 . . . . . . . . . . . .  4
   2.  Alternatives in IPv6 . . . . . . . . . . . . . . . . . . . . .  5
     2.1.  No Response  . . . . . . . . . . . . . . . . . . . . . . .  5
     2.2.  Wildcard match . . . . . . . . . . . . . . . . . . . . . .  5
     2.3.  Dynamic DNS  . . . . . . . . . . . . . . . . . . . . . . .  6
       2.3.1.  Dynamic DNS from Individual Hosts  . . . . . . . . . .  6
       2.3.2.  Dynamic DNS through Residential Gateways . . . . . . .  7
       2.3.3.  Dynamic DNS Delegations  . . . . . . . . . . . . . . .  7
       2.3.4.  Generate Dynamic Records . . . . . . . . . . . . . . .  8
       2.3.5.  Populate from DHCP Server  . . . . . . . . . . . . . .  8
       2.3.6.  Populate from RADIUS Server  . . . . . . . . . . . . .  9
     2.4.  Delegate DNS . . . . . . . . . . . . . . . . . . . . . . .  9
     2.5.  Dynamically Generate PTR When Queried ("On the Fly") . . .  9
   3.  Recommendations  . . . . . . . . . . . . . . . . . . . . . . . 10
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . . 10
     4.1.  Using Reverse DNS for Security . . . . . . . . . . . . . . 10
     4.2.  DNS Security with Dynamic DNS  . . . . . . . . . . . . . . 10
     4.3.  Considerations for Other Uses of the DNS . . . . . . . . . 11
   5.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 11
   6.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 11
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     7.1.  Normative References . . . . . . . . . . . . . . . . . . . 11
Show full document text