RFC 1034:DOMAIN NAMES - CONCEPTS AND FACILITIES
RFC-Ref

network


Click on the red underlined text to get to the source

... Host name to address mappings were maintained by the Network Information Center (NIC) in a single file (HOSTS ...
... hosts [RFC-952, RFC-953]. The total network bandwidth consumed in distributing a new version by this scheme is proportional to the square of the number of hosts ...
... scheme is proportional to the square of the number of hosts in the network, and even when multiple levels of FTP are used, the outgoing FTP ...
... The network population was also changing in character. The timeshared hosts that made up the original ARPANET ...
... hosts that made up the original ARPANET were being replaced with local networks of workstations. Local organizations were administering their own names and addresses ...
... caused by ad hoc encodings, names should not be required to contain network identifiers, addresses, routes, or similar ...
... Because we want the name space to be useful in dissimilar networks and applications, we provide the ability to use the same name space with different protocol families or ...
... simultaneously updated. When updates are unavailable due to network or host failure, the usual course is to believe old information while continuing efforts to update ...


... be as general as possible, so that it can be used to build arbitrary applications. In particular, the system was designed so that the name space did not have to be organized along the lines of network boundaries, name servers, etc. The rationale for this is not that the name space should have no implied ...
... IN-ADDR.ARPA domain is organized and distributed by network and host address because its role ...
... address because its role is to translate from network or host numbers to names; NetBIOS domains ...


... a network where we want to concentrate the cache rather than having a separate cache ...
... large, non-IP/TCP, network wanted to create a mail gateway. If the ...
... process when the primary is unavailable due to host downtime or network problems, or when a secondary server has better network access to an ...
... host downtime or network problems, or when a secondary server has better network access to an "intermediate" secondary than to the primary. ...


... A very important goal of the resolver is to eliminate network delay and name server load from most requests by answering them from its cache of ...
... In a less than perfect world, all resolvers will occasionally be unable to resolve a particular request. This condition can be caused by a resolver which becomes separated from the rest of the network due to a link failure or gateway problem, or less often by coincident failure or ...
... PC which lacks the resources to perform the resolver function, or can centralize the cache for a whole local network or organization. ...
... eventual access to all of the domain space. The two local servers will allow the resolver to continue to resolve local names if the local network becomes isolated from the internet due to gateway or link ...
... manner. The sorting can be a simple function of preferring addresses on the local network over others, or may involve statistics from past events, such as previous response times and batting averages. ...


... A.ISI.EDU is listed first on the assumption that the resolver orders its choices by preference, and A.ISI.EDU is on the same network. ...


... Quarterman, J., and J. Hoskins, "Notable Computer Networks",Communications of the ACM, October 1986, volume 29, number 10. ...
... K. Harrenstien, "NAME/FINGER", RFC-742(-> 1288draft | 1196(-> 1288draft) | 1194(-> 1288draft | 1196(-> 1288draft))), Network Information Center, SRI International, December 1977. ...
... Internet Host Table Specification", RFC-810(-> 952), Network Information Center, SRI International, March 1982. Obsolete. See RFC-952. ...
... K. Harrenstien, V. White, and E. Feinler, "Hostnames Server", RFC-811(-> 953hist), Network Information Center, SRI International, March 1982. Obsolete. See RFC-953hist. ...
... NICNAME/WHOIS", RFC-812(-> 3912draft | 954(-> 3912draft)), Network Information Center, SRI International, March 1982. ...
... Domain Naming Convention for Internet User Applications", RFC-819, Network Information Center, SRI International, August 1982.
Early thoughts on the design of the domain system. Current implementation is completely different. ...
... Internet Name Service", RFC-830, Network Information Center, SRI International, October 1982.
Early thoughts on the design of the domain system. Current implementation is completely different. ...
... M. Solomon, L. Landweber, and D. Neuhengen, "The CSNET Name Server", Computer Networks, vol 6, nr 3, July 1982.
Describes a name service for CSNET which is independent from the DNS ...



Google
Web
RFC-Ref