TL;DR: This RFC is the revised specification of the protocol and format used in the implementation of the Domain Name System and it obsoletes RFC-883.
Abstract: This RFC is the revised specification of the protocol and format used
in the implementation of the Domain Name System. It obsoletes RFC-883.
This memo documents the details of the domain name client - server
communication.
TL;DR: This memo describes the domain style names and their used for host address look up and electronic mail forwarding and discusses the clients and servers in the domain name system and the protocol used between them.
Abstract: This RFC is the revised basic definition of The Domain Name System. It
obsoletes RFC-882. This memo describes the domain style names and
their used for host address look up and electronic mail forwarding. It
discusses the clients and servers in the domain name system and the
protocol used between them.
TL;DR: This document introduces these extensions and describes their capabilities and limitations, and describes the interrelationships between the documents that collectively describe DNSSEC.
Abstract: The Domain Name System Security Extensions (DNSSEC) add data origin
authentication and data integrity to the Domain Name System. This
document introduces these extensions and describes their capabilities
and limitations. This document also discusses the services that the
DNS security extensions do and do not provide. Last, this document
describes the interrelationships between the documents that
collectively describe DNSSEC. [STANDARDS-TRACK]
TL;DR: A universal electronic resource denotation, request and delivery system as mentioned in this paper allows a user to locate information on a distributed computer system or network such as the Internet by knowing or guessing a short mnemonic alias of an electronic resource without the user having to know the physical or other location denotation.
Abstract: A universal electronic resource denotation, request and delivery system allows a user to locate information on a distributed computer system or network such as the Internet by knowing or guessing a short mnemonic alias of an electronic resource without the user having to know the physical or other location denotation such as the universal resource locator (URL) of the desired resource. The system hardware includes a client computer, a local server, a central registry server, a value added server, and a root server. The universal electronic resource denotation, request and delivery system supports a personal aliasing (nicknaming) feature, a universal resource accessing feature for finding location information such as URLs relating to a query term, a "see also" feature for including information about related documents or resources within the record of a resource, a feature for updating local servers and client machines by periodically deleting those records which have changed, a "try again" and "mirroring" feature for aiding a user in obtaining the resource under adverse hardware or software conditions, and an authentication and administration feature that allows a user to administer the aliases and related data which pertain to his/her resources.
TL;DR: The Domain Name System was originally designed to support queries of a statically configured database, but the frequency of changes was expected to be fairly low, and all updates were made as external edits to a zone's Master File.
Abstract: The Domain Name System was originally designed to support queries of a statically configured database. While the data was expected to change, the frequency of those changes was expected to be fairly low, and all updates were made as external edits to a zone's Master File.