DNS Delegation Requirements
draft-wallstrom-dnsop-dns-delegation-requirements-03

Document Type Expired Internet-Draft (dnsop WG)
Last updated 2017-04-29 (latest revision 2016-10-26)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-wallstrom-dnsop-dns-delegation-requirements-03.txt

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 (pawal@blipp.com)
Jakob Schlyter (jakob@kirei.se)

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