ARPA
Click on the red underlined text to get to the source
... environment.
The ARPA Internet illustrates the size-related problems; it is a
large system and is likely to grow much larger. The need to have
...
... 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
mechanisms. Currently hosts ...
... Internet
addresses (e.g., 10.2.0.52) is beginning to stress the existing
mechanisms. Currently hosts in the ARPA Internet are registered
with the Network ...
... query names the domain
name of interest and describes the type of resource information
that is desired. For example, the ARPA Internet uses some of
its domain names ...
... A special label is defined that matches any other label. This
label is the asterisk or "*". An asterisk matches a single label.
Thus *.ARPA matches FOO.ARPA, but does not match FOO.BAR.ARPA.
...
... label is the asterisk or "*". An asterisk matches a single label.
Thus *.ARPA matches FOO.ARPA, but does not match FOO.BAR.ARPA.
The asterisk is mainly used to create ...
... Thus *.ARPA matches FOO.ARPA, but does not match FOO.BAR.ARPA.
The asterisk is mainly used to create default resource records ...
... specifies the host having that address. Thus F.ISI.ARPA might
be the owner of a RR which specified an address ...
... A class field identifies the format of the resource data, such
as the ARPA Internet format (IN) or the Computer Science ...
... class specific information varies according to
the value in the CLASS field; for the ARPA Internet, it is the 32
bit ...
...
+----------+--------+--------+----------------------------+
|F.ISI.ARPA| A | IN | 10.2.0.52 |
+----------+--------+--------+----------------------------+
...
... and
+----------+--------+--------+----------------------------+
|F.ISI.ARPA| A | CS | 213-822-2112 |
+----------+--------+--------+----------------------------+
...
... domain name which names the resource record.
For example, F.ISI.ARPA might have two records of the form:
+----------+--------+--------+----------------------------+
...
...
+----------+--------+--------+----------------------------+
|F.ISI.ARPA| MD | IN | F.ISI.ARPA ...
... ARPA| MD | IN | F.ISI.ARPA |
+----------+--------+--------+----------------------------+
and
...
... and
+----------+--------+--------+----------------------------+
|F.ISI.ARPA| MF | IN | B.ISI.ARPA ...
... +----------+--------+--------+----------------------------+
These records mean that mail for F.ISI.ARPA can either be
delivered to the host F.ISI.ARPA ...
... ARPA can either be
delivered to the host F.ISI.ARPA or forwarded to B.ISI.ARPA, which
will accept responsibility for its eventual delivery ...
... delivered to the host F.ISI.ARPA or forwarded to B.ISI.ARPA, which
will accept responsibility for its eventual delivery. In
...
... +------------------+------------------+
| | |
DDN ARPA CSNET
| | |
+-----+-----+ | +-----+-----+
...
... hosts and other resources often have several
names that identify the same resource. For example, under current
ARPA Internet naming support, USC-ISIF and ISIF both identify the
same host ...
... Suppose a name server was processing a query with QNAME=ISIF.ARPA,
QTYPE=A, and QCLASS=IN, and had the following resource records ...
... RRs would be returned in the response.
In the above example, because ISIF.ARPA has no RRs other than the
CNAME ...
... CNAME RR, the resources associated with ISIF.ARPA will appear to
be exactly those associated with F.ISI.ARPA for the IN ...
... RR, the resources associated with ISIF.ARPA will appear to
be exactly those associated with F.ISI.ARPA for the IN CLASS.
...
... MF RR without any
information from F.ISI.ARPA. This structure might be used to send
mail addressed to XXXX.ARPA to A.ISI.ARPA ...
... information from F.ISI.ARPA. This structure might be used to send
mail addressed to XXXX.ARPA to A.ISI.ARPA and to direct TELNET for
...
... ARPA. This structure might be used to send
mail addressed to XXXX.ARPA to A.ISI.ARPA and to direct TELNET for
XXXX.ARPA ...
... domains. We might allocate name servers as follows:
|(B.ISI.ARPA)
|(UDEL.CSNET)
+------------------+------------------+
...
... +------------------+------------------+
| | |
DDN ARPA CSNET
|(JCS.DDN) |(F.ISI.ARPA) |(UDEL.ARPA ...
... ARPA) |(UDEL.ARPA)
+-----+-----+ |(A.ISI.ARPA)+-----+-----+
| | | | | |
JCS ARMY NAVY | UDEL UCI
...
...
Thus the root name servers are on B.ISI.ARPA and UDEL.CSNET, the
DDN name server is on JCS.DDN, the CSNET domain ...
... name server is on JCS.DDN, the CSNET domain server is on
UDEL.ARPA, etc.
In an actual system, all domains ...
... In an actual system, all domains should have redundant name
servers, but in this example only the ARPA domain has redundant
servers A.ISI.ARPA ...
... domain has redundant
servers A.ISI.ARPA and F.ISI.ARPA. (The B.ISI.ARPA and UDEL.CSNET
name servers happen to be not redundant because they handle
...
... servers A.ISI.ARPA and F.ISI.ARPA. (The B.ISI.ARPA and UDEL.CSNET
name servers happen to be not redundant because they handle
different classes ...
... name servers happen to be not redundant because they handle
different classes.) The F.ISI.ARPA name server has authority over
...
... B.ISI.ARPA Name server for " " ...
... IN.
The contents of the SOA resource record point back to A.ISI.ARPA
and denote that the master data for the zone of authority is
...
... authority. The NS root entry for the B.ISI.ARPA
name server is necessary so that this name server ...
... CS class root. UDEL.CSNET and UDEL.ARPA may or may not
refer to the same name server; from this information it is
...
... query specifying QTYPE=MAILA,
QCLASS=IN, QNAME=F.ISI.ARPA, it would begin processing (using the
previous algorithm) by determining that it was not an authority ...
... algorithm) by determining that it was not an authority
for F.ISI.ARPA. The test would note that it had authority at " ",
but would also note that the authority ...
... authority at " ",
but would also note that the authority was delegated at ARPA and
never reestablished via another SOA. Thus the response would
return the NS ...
... IN class, the SOA RR for ARPA denotes that this name
server is authoritative for the domain ARPA ...
... ARPA denotes that this name
server is authoritative for the domain ARPA, and that the master
file for this authority is stored on B.ISI.ARPA ...
... ARPA, and that the master
file for this authority is stored on B.ISI.ARPA. This zone
extends to ISI.ARPA, where the database ...
... authority is stored on B.ISI.ARPA. This zone
extends to ISI.ARPA, where the database delegates authority back
...
... name server received a query of the form
QNAME=A.ISI.ARPA, QTYPE=A, and QCLASS=IN. The authority search ...
... at ISI.ARPA, and the reassumption of authority at ISI.ARPA. Hence
it would know that it was an authority for this query ...
... query. It would
then find the A record for A.ISI.ARPA, and return a datagram
containing this record.
...
...
Another query might be QNAME=B.ISI.ARPA, QTYPE=MAILA, QCLASS=*.
In this case the name server would know that it cannot be
...
... authoritative because of the "*" value of QCLASS, and would look
for records for domain B.ISI.ARPA that match. Assuming that the
name server performs the additional record inclusion mentioned in
...
... name server would discover that AI.MIT.ARPA was the authoritative
name server and return the following:
...
... In this case, the requestor is directed to seek information from
the MIT.ARPA domain name server residing on AI.MIT.ARPA ...
... UDEL.ARPA and UDEL.CSNET name server ...
... discussion of the sample domain, we stated that
UDEL.CSNET and UDEL.ARPA might be the same name server. In this
example, we assume that this is the case. As such, the name
server ...
...
This name server deals with mail forwarding between the ARPA
Internet and CSNET systems. Its RRs ...
... query for
an arbitrary host on the ARPA Internet, it must consult a set of
name servers sufficient to know that all IN ...
... QCLASS=IN and a RR for ISI.ARPA. This request asks for completion
for a resource whose name begins with "B" and is "close" to
ISI.ARPA ...
... ARPA. This request asks for completion
for a resource whose name begins with "B" and is "close" to
ISI.ARPA. This might be a typical shorthand used in the ISI
community which uses "B" as a way of referring to B.ISI.ARPA.
...
... ISI.ARPA. This might be a typical shorthand used in the ISI
community which uses "B" as a way of referring to B.ISI.ARPA.
The first step in processing a completion request is to look for a
...
... search
would not match BB.ARPA to B, but this search would. If multiple
hits are found, the same discarding strategy is followed.
...