address
Click on the red underlined text to get to the source
... style names, their use for Internet mail and
host address support, and the protocols and servers used to implement
domain name facilities.
...
... networks of workstations. Local
organizations were administering their own names and
addresses, but had to wait for the NIC to change HOSTS.TXT to
...
... generally useful, and not restricted to a single application.
We should be able to use names to retrieve host addresses,
mailbox data, and other as yet undetermined information. All
...
... management. For example, host address formats differ between
protocols, though all protocols have the notion of address.
...
... host address formats differ between
protocols, though all protocols have the notion of address.
The DNS tags ...
... class as well as the type, so
that we can allow parallel use of different formats for data
of type address.
...
... mailbox bindings, host addresses), but that the system should
be able to deal with subsets that change more rapidly (on the
order of seconds or minutes). ...
... together with RR formats for describing host addresses, etc. Because we
need a reliable inverse mapping from address to host name ...
... host addresses, etc. Because we
need a reliable inverse mapping from address to host name, a special
mapping for addresses ...
... address to host name, a special
mapping for addresses into the IN-ADDR.ARPA domain is also defined.
...
...
For mailboxes, the mapping is slightly more complex. The usual mail
address <local-part>@<mail-domain> is mapped into a domain name by
...
... domain name. The address RRs use a standard IP address
format to contain a 32 bit internet address ...
... the primary name and not the alias. This avoids extra indirections in
accessing information. For example, the address to name RR for the
above host ...
...
Because the server assumes that if the requester wants mail exchange
information, it will probably want the addresses of the mail exchanges
soon afterward.
...
... domain name
rather than by host address or any other resource type. Inverse queries
are primarily useful for debugging and database ...
... TTL, and do not indicate cases
where the identified RR is one of a set (for example, one address for a
host having multiple addresses). Therefore, the ...
... is one of a set (for example, one address for a
host having multiple addresses). Therefore, the RRs returned in inverse
queries should never be cached.
...
... queries are NOT an acceptable method for mapping host addresses
to host names; use the IN-ADDR.ARPA ...
... RRs that name the
servers for subzones are often not enough for this task since they name
the servers, but do not give their addresses. In particular, if the
name of the name server is itself in the subzone, we could be faced with
...
... NS RRs tell us that in order to learn a name
server's address, we should contact the server using the address we wish
to learn. To fix this problem, a zone contains "glue" RRs ...
... RRs tell us that in order to learn a name
server's address, we should contact the server using the address we wish
to learn. To fix this problem, a zone contains "glue" RRs which are not
...
... to learn. To fix this problem, a zone contains "glue" RRs which are not
part of the authoritative data, and are address RRs for the servers.
These RRs ...
... RRs for the subzone into the authority
section of the reply. Put whatever addresses are
available into the additional section, using glue RRs
...
... available into the additional section, using glue RRs
if the addresses are not available from authoritative
data or the cache. Go to step 4.
...
... caller wants
one or more 32 bit IP addresses. Under the DNS, it
translates into a request for type A RRs ...
... not preserve the order of RRs, this function may choose to
sort the returned addresses or select the "best" address if
the service ...
... RRs, this function may choose to
sort the returned addresses or select the "best" address if
the service returns only one choice to the client ...
... service returns only one choice to the client. Note that
a multiple address return is recommended, but a single
address may be the only way to emulate prior HOSTS ...
... a multiple address return is recommended, but a single
address may be the only way to emulate prior HOSTS.TXT
services ...
... This function will often follow the form of previous
functions. Given a 32 bit IP address, the caller wants a
character string. The octets of the IP address ...
... IP address, the caller wants a
character string. The octets of the IP address are reversed,
used as name components, and suffixed with "IN-ADDR.ARPA". A
...
... host. For example, a request for the host name
corresponding to IP address 1.2.3.4 looks for PTR RRs for
domain name ...
... This happens when the referenced name exists, but data of the
appropriate type does not. For example, a host address
function applied to a mailbox name would return this error
...
... function applied to a mailbox name would return this error
since the name exists, but no address RR is present.
...
... It is important to note that the functions for translating between host
names and addresses may combine the "name error" and "data not found"
error conditions into a single type of error return, but the general
...
... alias. For example, the resolver might
find that the name given for host name to address translation is an
alias when it finds the CNAME ...
...
All that the remaining stub needs is a list of name server addresses
that will perform the recursive requests. This type of resolver
presumably needs the information in a configuration file ...
... changes the guess. This structure includes the
equivalent of a zone name, the known name servers for
the zone, the known addresses for the name servers, and
history information which can be used to suggest which
server is likely to be the best one to try next. The
...
... RRs list the names of hosts for a zone at or above SNAME. Copy
the names into SLIST. Set up their addresses using local data. It may
be the case that the addresses are not available. The resolver has many
...
... the names into SLIST. Set up their addresses using local data. It may
be the case that the addresses are not available. The resolver has many
choices here; the best is to start parallel resolver processes looking
...
... start parallel resolver processes looking
for the addresses while continuing onward with the addresses which are
available. Obviously, the design choices and options are complicated
...
...
for the addresses while continuing onward with the addresses which are
available. Obviously, the design choices and options are complicated
and a function of the local host ...
... failure.
In addition to the names and addresses of the servers, the SLIST data
structure can be sorted to use the best servers first, and to insure
that all addresses ...
... addresses of the servers, the SLIST data
structure can be sorted to use the best servers first, and to insure
that all addresses of all servers are used in a round-robin manner. The
sorting can be a simple function of preferring addresses ...
... addresses of all servers are used in a round-robin 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.
...
... Step 3 sends out queries until a response is received. The strategy is
to cycle around all of the addresses for all of the servers with a
timeout between each transmission. In practice it is important to use
all addresses ...
... addresses for all of the servers with a
timeout between each transmission. In practice it is important to use
all addresses of a multihomed host, and too aggressive a retransmission
...
...
delegation RRs and any address RRs for the servers should be cached.
The name servers are entered in the SLIST, and the search ...
... RRs for
the servers host addresses, are not part of the authoritative data in
the zone, and hence have explicit TTLs.
...
... AA) bit is set
indicating that the address RRs in the answer section are from
authoritative data. The question section of the response matches the
...
... This response contains the MX RR in the answer section of the response.
The additional section contains the address RRs because the name server
...
... RRs because the name server
at C.ISI.EDU guesses that the requester will need the addresses in order
to properly use the information carried by the MX.
...
... If the same query was sent to C.ISI.EDU, its response might be the same
as shown above if it had its own address in its cache, but might also
be:
...
...
This information specifies servers to try, their addresses, and a match
count of -1, which says that the servers aren't very close to the
target. Note that the -1 isn't supposed to be an accurate closeness
...
...
At this point the resolver would need to pick one of the three available
addresses to try. Given that the resolver is on net 26, it should
choose either 26.0.0.73 or 26.3.0.103 as its first choice. It would
then send off a query ...
... The resolver would then wait for a response to its query or a timeout.
If the timeout occurs, it would try different servers, then different
addresses of the same servers, lastly retrying addresses already tried.
It might eventually receive a reply from SRI-NIC ...
... or a timeout.
If the timeout occurs, it would try different servers, then different
addresses of the same servers, lastly retrying addresses already tried.
It might eventually receive a reply from SRI-NIC.ARPA ...
... 952, SRI, October 1985. Specifies the format of HOSTS.TXT, the host/address table replaced by the DNS. ...