Address-specific DNS aliases (ANAME)
draft-ietf-dnsop-aname-04
| Document | Type | Expired Internet-Draft (dnsop WG) | |
|---|---|---|---|
| Last updated | 2020-01-09 (latest revision 2019-07-08) | ||
| Replaces | draft-hunt-dnsop-aname | ||
| Stream | IETF | ||
| Intended RFC status | Proposed Standard | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Yes | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-ietf-dnsop-aname-04.txt
Abstract
This document defines the "ANAME" DNS RR type, to provide similar functionality to CNAME, but only for address queries. Unlike CNAME, an ANAME can coexist with other record types. The ANAME RR allows zone owners to make an apex domain name into an alias in a standards compliant manner.
Authors
Tony Finch
(dot@dotat.at)
Evan Hunt
(each@isc.org)
Peter van Dijk
(peter.van.dijk@powerdns.com)
Anthony Eden
(anthony.eden@dnsimple.com)
Matthijs Mekking
(matthijs@isc.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)