CNAME+DNAME Name Redirection
draft-sury-dnsop-cname-plus-dname-01

Document Type Active Internet-Draft (individual)
Last updated 2018-07-15
Replaces draft-sury-dnsext-cname-at-apex, draft-sury-dnsext-cname-dname
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
dnsop                                                            O. Sury
Internet-Draft                               Internet Systems Consortium
Updates: 1034 (if approved)                                July 15, 2018
Intended status: Standards Track
Expires: January 16, 2019

                      CNAME+DNAME Name Redirection
                  draft-sury-dnsop-cname-plus-dname-01

Abstract

   This document updates RFC1034 to allow coexistence of the CNAME
   Resource Record with DNAME Resource Record at the same owner node,
   which provides redirection for a sub-tree of the domain name tree in
   the DNS system, in a parent zone.  By allowing this cooexistence, DNS
   system will have a way how to create a sub-tree redirection together
   that includes the Resource Records owner name.  This would allow
   parent zones to create full domain aliases.

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 https://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 January 16, 2019.

Copyright Notice

   Copyright (c) 2018 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
   (https://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

Sury                    Expires January 16, 2019                [Page 1]
Internet-Draft              CNAME-PLUS-DNAME                   July 2018

   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Requirements Language . . . . . . . . . . . . . . . . . .   3
   2.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  CNAME+DNAME Bundle  . . . . . . . . . . . . . . . . . . . . .   4
   4.  Query processing  . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Processing by Authoritative Servers . . . . . . . . . . .   4
     4.2.  Processing by Recursive Servers . . . . . . . . . . . . .   4
   5.  Implementation Report . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   RFC 1034 [RFC1034] defines CNAME resource record for cases when there
   are multiple names for single host.  A CNAME resource record
   identifies its owner name as an alias, and specifies the
   corresponding canonical name in the RDATA section of the resource
   record.  If a CNAME resource record is present at a node, no other
   data MUST be present; this ensures that the data for a canonical name
   and its aliases cannot be different.  This rule also insures that a
   cached CNAME can be used without checking with an authoritative
   server for other resource record types.

   However there is already existing exceptions to this rule.  RFC 4034
   [RFC4034] defines exception to RRSIG and NSEC records, which MUST
   exist for the same name as a CNAME resource record in a signed zone.

   RFC 6672 [RFC6672] defines DNAME resource record, which provides
   redirection for a sub-tree of the domain name tree in the DNS system.
   That is, all names that end with a particular suffix are redirected
   to another part of the DNS.

   The DNAME RR and the CNAME RR RFC 1034 [RFC1034] cause a lookup to
   (potentially) return data corresponding to a domain name different
   from the queried domain name.  The difference between the two
   resource records is that the CNAME RR directs the lookup of data at
   its owner to another single name, a DNAME RR directs lookups for data

Sury                    Expires January 16, 2019                [Page 2]
Show full document text