dns rfc documents from the ietf

The technical operation of the internet is governed by numerous documents. Each governing document is known as a Request for Comment(RFC) These documents are published under the auspices of the Internet Engineering Task Force(IETF).

edgedirector.com does not ask that you understand these documents. They are stored here as reference documents for your convenience.

Managed DNS hosting services from edgedirector.com are compliant with all applicable dns rfc documents.

The most important of the dns rfc documents are:

RFC 1034 - DOMAIN NAMES - CONCEPTS AND FACILITIES

This RFC is an introduction to the Domain Name System (DNS), and omits many details which can be found in a companion RFC, "Domain Names - Implementation and Specification" [RFC-1035]. That RFC assumes that the reader is familiar with the concepts discussed in this memo.

RFC 1035 - DOMAIN NAMES - IMPLEMENTATION AND SPECIFICATION

This RFC describes the details of the domain system and protocol, and assumes that the reader is familiar with the concepts discussed in a companion RFC, "Domain Names - Concepts and Facilities" [RFC-1034].

RFC 2181 - CLARIFICATIONS TO THE DNS SPECIFICATION

This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. Eight separate issues are considered.

RFC 2317 - CLASSLESS IN-ADDR.ARPA DELEGATION

This document describes a way to do IN-ADDR.ARPA delegation on non- octet boundaries for address spaces covering fewer than 256 addresses. The proposed method should thus remove one of the objections to subnet on non-octet boundaries but perhaps more significantly, make it possible to assign IP address space in smaller chunks than 24-bit prefixes, without losing the ability to delegate authority for the corresponding IN-ADDR.ARPA mappings. The proposed method is fully compatible with the original DNS lookup mechanisms specified in [1], i.e. there is no need to modify the lookup algorithm used, and there should be no need to modify any software which does DNS lookups.

RFC 3172 - MANAGEMENT GUIDELINES & OPERATIONAL REQUIREMENTS FOR THE ADDRESS AND ROUTING PARAMETER AREA DOMAIN ("ARPA")

This memo describes the management and operational requirements for the address and routing parameter area ("arpa") domain. The "arpa" domain is used to support a class of infrastructural identifier spaces, providing a distributed database that translates elements of a structured name space derived from a protocol family to service names. The efficient and reliable operation of this DNS space is essential to the integrity of operation of various services within the Internet. The Internet Architecture Board (IAB) has the responsibility, in cooperation with the Internet Corporation for Assigned Names and Numbers (ICANN), to manage the "arpa" domain. This document describes the principles used by the IAB in undertaking this role.

RFC 3568 - KNOWN CONTENT NETWORK (CN) REQUEST-ROUTING MECHANISMS

This document presents a summary of Request-Routing techniques that are used to direct client requests to surrogates based on various policies and a possible set of metrics. The document covers techniques that were commonly used in the industry on or before December 2000. In this memo, the term Request-Routing represents techniques that is commonly called content routing or content redirection. In principle, Request-Routing techniques can be classified under: DNS Request-Routing, Transport-layer Request-Routing, and Application-layer Request-Routing.

source: edgedirector.com