Updating Parent Zones
draft-andrews-dnsop-update-parent-zones-04
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Mark Andrews | ||
| Last updated | 2014-05-10 (latest revision 2013-11-06) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| 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-andrews-dnsop-update-parent-zones-04.txt
https://www.ietf.org/archive/id/draft-andrews-dnsop-update-parent-zones-04.txt
Abstract
DNS UPDATE was developed to allow DNS zones to be updated. There is a perception that UPDATE cannot be used in conjuction with the Registry, Registar, Registrant (RRR) model to update a zone. This document explains how UPDATE can be used in the RRR model.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)