DNS Delegation Requirements
draft-wallstrom-dnsop-dns-delegation-requirements-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Patrik Wallstrom , Jakob Schlyter | ||
| Last updated | 2021-06-25 (Latest revision 2016-10-26) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document outlines a set of requirements on a well-behaved DNS delegation of a domain name. A large number of tools have been developed to test DNS delegations, but each tool uses a different set of requirements for what is a correct setup for a delegated domain name. However, there are few requirements on how to set up DNS in order to just make the delegation work. In order to have a well- behaved delegation that is robust to failures and also makes DNS resolvers behave consistently, there are a large number of things to consider. Based on this document, it should be possible to set up a fully functional DNS delegation for a domain name, but also to create a set of test specifications for how to test a DNS delegation.
Authors
Patrik Wallstrom
Jakob Schlyter
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)