− | The need for a hierarchical [[DNS]] arose with the popularity of the Internet in academic spheres in the early 1980s. This eventually necessitated a de-centralized Internet. Communications between [[The Stanford Research Institute NIC]] and other institutions include plans to create a hierarchical [[DNS]], found in [[http://www.rfc-editor.org/rfc/rfc805.txt RFC 805]], a group document from 1982. This document outlines many of the basics of the eventual [[DNS]], including the need for [[TLD]]s to provide a fixed starting point for queries, and the need for [[SLD]]s to be unique. This, in turn, would necessitate the need for a [[registrar]] type of administration, and help the nascent [[IT]] community recognize that the distribution of responsibility for each domain to individual name servers would provide administrative advantages.<ref>[http://www.livinginternet.com/i/iw_dns_history.htm Living Internet] | + | The need for a hierarchical [[DNS]] arose with the popularity of the Internet in academic spheres in the early 1980s. This eventually necessitated a de-centralized Internet. Communications between [[The Stanford Research Institute NIC]] and other institutions include plans to create a hierarchical [[DNS]], found in [[http://www.rfc-editor.org/rfc/rfc805.txt RFC 805]], a group document from 1982. This document outlines many of the basics of the eventual [[DNS]], including the need for [[TLD]]s to provide a fixed starting point for queries, and the need for [[SLD]]s to be unique. This, in turn, would necessitate the need for a [[registrar]] type of administration, and help the nascent [[IT]] community recognize that the distribution of responsibility for each domain to individual name servers would provide administrative advantages.<ref>[http://www.livinginternet.com/i/iw_dns_history.htm Living Internet]</ref> |