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

The information below is for an old version of the document
Document Type Active Internet-Draft (dnsop WG)
Last updated 2015-12-02 (latest revision 2015-10-16)
Replaces draft-howard-isp-ip6rdns
Stream IETF
Intended RFC status Informational
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document
Document shepherd Tim Wicinski
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Tim Wicinski" <tjw.ietf@gmail.com>
Network Working Group                                          L. Howard
Internet-Draft                                         Time Warner Cable
Intended status: Informational                          October 16, 2015
Expires: April 18, 2016

           Reverse DNS in IPv6 for Internet Service Providers
                    draft-ietf-dnsop-isp-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 and
   considerations for ISPs in managing 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 18, 2016.

Copyright Notice

   Copyright (c) 2015 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

Howard                   Expires April 18, 2016                 [Page 1]
Internet-Draft        draft-ietf-dnsop-isp-ip6rdns          October 2015

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Reverse DNS in IPv4 . . . . . . . . . . . . . . . . . . .   3
     1.2.  Reverse DNS Considerations in IPv6  . . . . . . . . . . .   3
   2.  Alternatives in IPv6  . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Negative Response . . . . . . . . . . . . . . . . . . . .   4
     2.2.  Wildcard match  . . . . . . . . . . . . . . . . . . . . .   5
     2.3.  Dynamic DNS . . . . . . . . . . . . . . . . . . . . . . .   5
       2.3.1.  Dynamic DNS from Individual Hosts . . . . . . . . . .   6
       2.3.2.  Dynamic DNS through Residential Gateways  . . . . . .   6
       2.3.3.  Automatic 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 . . . . . . . . . . . . .   8
     2.4.  Delegate DNS  . . . . . . . . . . . . . . . . . . . . . .   8
     2.5.  Dynamically Generate PTR When Queried ('On the Fly')  . .   9
   3.  Considerations and Recommendations  . . . . . . . . . . . . .   9
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
     4.1.  Using Reverse DNS for Security  . . . . . . . . . . . . .  10
     4.2.  DNS Security with Dynamic DNS . . . . . . . . . . . . . .  11
     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
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  12
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   Best practice is that "Every Internet-reachable host should have a
   name" [RFC1912] that is recorded with a PTR resource record in the
   .ARPA zone, and "PTR's should use official names and not aliases"
   [RFC1033].  Some network services perform a PTR lookup on the source
   address of incoming packets before performing services.

   Individual Internet users in the residential or consumer scale,
   including small and home businesses, are constantly joining or moving
   on the Internet.  For large Internet service providers who serve
   residential users, maintenance of individual PTR records is
   impractical.  Administrators at ISPs should consider the need for PTR
   records and evaluate methods for responding to reverse DNS queries in
Show full document text