RFC 882:DOMAIN NAMES - CONCEPTS and FACILITIES
RFC-Ref

host


Click on the red underlined text to get to the source

... domain names As applications grow to span multiple hosts, then networks, and finally internets, these applications must also span multiple ...
... Internet illustrates the size-related problems; it is a large system and is likely to grow much larger. The need to have a mapping between host names (e.g., USC-ISIF) and ARPA Internet addresses (e.g., 10.2.0.52) is beginning to stress the existing ...
... ARPA Internet addresses (e.g., 10.2.0.52) is beginning to stress the existing mechanisms. Currently hosts in the ARPA Internet are registered ...
... Network Information Center (NIC) and listed in a global table (available as the file <NETINFO>HOSTS.TXT on the SRI-NIC host ...
... HOSTS.TXT on the SRI-NIC host) [1]. The size of this table, and especially the frequency of updates to the table are near the limit of manageability. What ...
... mailbox. Some of these methods involve the use of routes and forwarding hosts as part of the mail destination address, and consequently force the mail user to know multiple address ...
... The costs of implementing such a facility dictate that it be generally useful, and not restricted to a single application. We should be able to use names to retrieve host addresses, mailbox ...
... Internet uses some of its domain names to identify hosts; queries for address ...
... resources return ARPA Internet host addresses. However, to preserve the generality of the domain ...
... domain names are not required to have a one-to-one correspondence with host names, host addresses, or any other type of information. ...
... are not required to have a one-to-one correspondence with host names, host addresses, or any other type of information. ...
... The size of the total database will initially be proportional to the number of hosts using the system, but will eventually grow to be proportional to the number of users on those hosts ...
... to the number of hosts using the system, but will eventually grow to be proportional to the number of users on those hosts as mailboxes and other information are added to the domain ...
... mailbox bindings, host addresses), but that the system should be able to deal with subsets that change more rapidly (on the ...
... for the database will usually correspond to organizations that have one or more hosts. Each organization that has responsibility for a particular set of domains will provide ...
... responsibility for a particular set of domains will provide redundant name servers, either on the organization's own hosts or other hosts that the organization arranges to use. ...
... redundant name servers, either on the organization's own hosts or other hosts that the organization arranges to use. Clients ...
... unavailable due to network or host failure, the usual course is to believe old information while continuing efforts to update it. The general ...
... The domain system assumes that all data originates in master files scattered through the hosts that use the domain system. These master files are updated by local system ...
... 14]. The standard format allows these files to be exchanged between hosts (via FTP, mail, or some other mechanism); this facility is useful when an organization wants a domain ...
... support a name server. The organization can maintain the master files locally using a text editor, transfer them to a foreign host which runs a name server, and then arrange with the system administrator ...
... Each host's name servers and resolvers are configured by a local system administrator. For a name server ...


... record, and hence the "owner" of the information. For example, a RR that specifies a host address has a domain name the ...
... address has a domain name the specifies the host having that address. Thus F.ISI.ARPA might ...
... in this resource record. Types refer to abstract resources such as host addresses or mail delivery agents. The type field ...
... and pass on records which they cannot interpret. The format of the internal data is restricted only by the maximum length of 65535 octets; for example the host address record might specify a fixed 32 bit ...
... agent identification from details of how to contact the agent (e.g. host addresses). ...
... This memo uses the following types in its examples: A - the host address associated with the domain name ...
... The first type of resource record holds a host name to host address binding ...
... The first type of resource record holds a host name to host address binding. Its fields are: ...
... bit ARPA Internet address of the host, for the CSNET it might be the phone number of the host ...
... host, for the CSNET it might be the phone number of the host. For example, F.ISI.ARPA might have two A records ...
... The <domain name> field is a domain name of the host that will handle mail; note that this domain name may be completely ...
... These records mean that mail for F.ISI.ARPA can either be delivered to the host F.ISI.ARPA or forwarded to B.ISI.ARPA, which ...
... principle, an additional name lookup is required to map the domain name of the host to the appropriate address, in practice this information is usually returned in the response to the mail query ...


... name server for a domain reside in a host which has a name in the same domain, although this will usually be the case. There is also no restriction on the number ...
... method is to store the information acquired by a resolver when the resolver consults other name servers. In a sophisticated host, the resolver and name server will coordinate their actions and use a shared database ...
... update the domain related information, and to resolve any problems (e.g., protocol violations) with hosts in the domain. ...
... servers must be accessible from outside the domain (as well as inside) and must resolve names for at least all the hosts in the domain. ...
... The appropriate information is defined in [14], but generally consists of host to address bindings for domain names in returned ...
... In existing systems, hosts and other resources often have several names that identify the same resource. For example, under current ARPA ...
... ARPA Internet naming support, USC-ISIF and ISIF both identify the same host. Similarly, in the case of mailboxes, many organizations provide many names that actually go to the same ...
... IN class mail forwarding for all hosts in the CSNET domain without IN ...
... and denote that the master data for the zone of authority is originally from this host. The first three NS records denote delegation ...
... query might map a domain name to a host address, the corresponding inverse query might map the ...
... domain system is organized by domain name rather than by host address or any other resource type. In general, a resolver or other program that wishes to ...
... For example, if a resolver wishes to perform an inverse query for an arbitrary host on the ARPA Internet, it must consult a set of ...
... system to fill in other arguments. For example, many mail systems allow the user to specify a username without a host for local mail delivery. ...


... FTP) in the form of a subroutine call, system call etc., and returns the desired information in a form compatible with the local host's data formats. ...
... name server, and should know the authoritative name server for the host that it services. ...
... classes supported by the client. Note that in either case, the resolver must understand the preferences of the host. For example, the host that supports both CSNET and ARPA ...
... case, the resolver must understand the preferences of the host. For example, the host that supports both CSNET and ARPA ...


... The labels must follow the rules for ARPANET host names. They must start with a letter, end with a letter or digit, and have as interior ...
... restrictions on the length. Labels must be 63 characters or less. For example, the following strings identify hosts in the ARPA Internet ...


... E. Feinler, K. Harrenstien, Z. Su, and V. White, "DOD Internet Host Table Specification", RFC 810(-> 952), Network Information Center, SRI International, March 1982. ...



Google
Web
RFC-Ref