domain
Click on the red underlined text to get to the source
... This RFC proposes two extensions to the Domain Name System: ...
... network names. Although it would be possible to provide a flat space
or a name space in which, for example, the last label of a domain
name captured the old-style network name, any such approach would add
complexity to the method ...
... create network names in any
domain under his control, and also create network number to name
...
... network number to name
entries in IN-ADDR.ARPA domains under his control. Thus, the name
for the ARPANET might become NET.ARPA ...
...
The network name syntax discussed above can provide domain names
which will contain mappings from network names to various quantities,
...
... secondary advantage is that it uses names which are not in use
already, and hence it is possible to test whether an
organization has entered this information in its domain
database.
...
... In general, this information will be added to an existing
master file for some IN-ADDR.ARPA domain for each network
involved. Similar RRs ...
...
In general, this information will be inserted in the master
file for the domain name of the organization; this is a
different file from that which holds the information below
IN-ADDR.ARPA ...
...
The term "Yellow Pages" is used in almost as many ways as the term
"domain", so it is useful to define what is meant herein by YP. The
general problem to be solved is to create a method ...
... build the index. For example, it is impractical to search the entire
domain tree to find a particular address RR ...
... Such a precomputed index is what we mean by YP, and we regard the
IN-ADDR.ARPA domain as the first instance of a YP in the DNS.
Although a single, centrally-managed YP for well-known ...
...
Following the IN-ADDR example, the YP takes the form of a domain tree
organized to optimize retrieval by search ...
...
This ordering reflects the natural scoping of control, and hence the
order of the components in a domain name. Thus domain names would be
of the form:
...
... This ordering reflects the natural scoping of control, and hence the
order of the components in a domain name. Thus domain names would be
of the form:
...
... these metavariables, as well as encoding rules for converting a
<from-value> into a domain name. We might define:
...
... Reversed 4-octet decimal string
Name Domain name
...
...
As a practical matter, we might want to create both of these domains
to enable users on the Internet to experiment with centrally
...
...
We could imagine that all conversion routines using these YPs might
be instructed to use "YP.<local-domain>" followed by "YP." as a
search list. Thus, if the organization ISI.EDU wished to define
...
... RRs
which map back and forth by deleting the origin. This could be done
either by allowing the domain name in the RDATA portion to not
identify a real domain name ...
... domain name in the RDATA portion to not
identify a real domain name, or by defining a new RR which used a
simple text string rather than a domain name ...
... domain name, or by defining a new RR which used a
simple text string rather than a domain name.
...
... ideas in this RFC. Numerous contributions, criticisms, and
compromises were produced in the IETF Domain working group and the
NAMEDROPPERS mailing list ...
... Mockapetris, P., "Domain names - Concepts and Facilities", RFC 882(-> 1035std13 | 1034std13), USC/Information Sciences Institute, November 1983. Superseded by RFC 1034std13. ...
... Mockapetris, P.,"Domain names - Implementation and Specification", RFC 883(-> 1035std13 | 1034std13), USC/Information Sciences Institute, November 1983. Superceeded by RFC 1035std13. ...
... Postel, J. and J. Reynolds, "Domain Requirements", RFC 920, October 1984. Explains the naming scheme for top level domains ...
... Domain Requirements", RFC 920, October 1984. Explains the naming scheme for top level domains. ...
... Mockapetris, P., "Domain System Changes and Observations", RFC 973(-> 1035std13 | 1034std13), USC/Information Sciences Institute, January 1986. Describes changes to RFCs 882 and 883 and reasons for them. ...
... Partridge, C., "Mail routing and the domain system", RFC 974(-> 2821prop), CSNET CIC BBN Labs, January 1986. Describes the transition from HOSTS.TXT based mail addressing ...
... 974(-> 2821prop), CSNET CIC BBN Labs, January 1986. Describes the transition from HOSTS.TXT based mail addressing to the more powerful MX system used with the domain system. ...
... Mockapetris, P., "Domain names - Concepts and Facilities", RFC 1034std13, USC/Information Sciences Institute, November 1987. Introduction/overview of the DNS. ...
... Mockapetris, P., "Domain names - Implementation and Specification", RFC 1035std13, USC/Information Sciences Institute, November 1987. DNS implementation instructions. ...