CNAME at the zone apex
draft-sury-dnsext-cname-at-apex-00

Document Type Replaced Internet-Draft (individual)
Last updated 2010-08-18
Replaced by draft-sury-dnsop-cname-plus-dname
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-sury-dnsop-cname-plus-dname
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-sury-dnsext-cname-at-apex-00.txt

Abstract

This document proposes a modification to CNAME record to coexist with SOA and NS records at the zone apex. This proposal will improve aliasing in the DNS system. The users are often forced to manually add duplicate A, AAAA and MX records by copying data from the target zone to the aliased zone. This forces zone owner to keep track of target domain name since the mismatch in the data could cause failures. This administrative burden will be eliminated by allowing CNAME to coexist with NS and SOA resource records.

Authors

Ondřej Surý (ondrej.sury@nic.cz)

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