CNAME at the zone apex
draft-sury-dnsext-cname-at-apex-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Ondřej Surý | ||
| Last updated | 2010-08-18 | ||
| Replaced by | draft-sury-dnsop-cname-plus-dname | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
html
xml
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
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
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)