service
Click on the red underlined text to get to the source
... classes, functions, etc. Thus while the components
of the official protocol are expected to stay essentially unchanged and
operate as a production service, experimental behavior should always be
expected in extensions beyond the official protocol. Experimental ...
... Internet were getting more
sophisticated and creating a need for general purpose name
service.
...
... organized into units called ZONEs, and these zones can be
automatically distributed to the name servers which provide
redundant service for the data in a zone.
...
... label, you should preserve its case. The rationale for this choice is
that we may someday need to add full binary domain names for new
services; existing services would not be changed.
...
... that we may someday need to add full binary domain names for new
services; existing services would not be changed.
...
... result. Of course, the possible questions which can be asked in a query
does shape the kind of service a resolver can provide.
...
...
Implementation of this service is optional in a name server, but all
name servers must at least be able to understand an inverse query ...
...
The optional completion services described in RFCs 882(-> 1035std13 | 1034std13) and 883(-> 1035std13 | 1034std13) have been
...
... and 883(-> 1035std13 | 1034std13) have been
deleted. Redesigned services may become available in the future, or the
opcodes may be reclaimed for other use.
...
... role of a resolver and
returns either an error or the answer, but never referrals.
This service is optional in a name server, and the name server
...
...
Recursive service is helpful in several situations:
...
...
Non-recursive service is appropriate if the requester is capable of
pursuing referrals and interested in information which will aid future
requests.
...
... name server in all responses. The bit is true if the name
server is willing to provide recursive service for the client,
regardless of whether the client ...
... client,
regardless of whether the client requested recursive service.
That is, RA signals availability rather than use.
...
... bit specifies specifies whether the requester wants recursive
service for this query. Clients may request recursive service ...
... service for this query. Clients may request recursive service
from any name server, though they should depend upon receiving ...
... it only from servers which have previously sent an RA, or
servers which have agreed to provide service through private
agreement or some other means outside of the DNS ...
... query with RD set arrives at a server
which is willing to provide recursive service; the client can verify
that recursive mode was used by checking that both RA ...
... are set in
the reply. Note that the name server should never perform recursive
service unless asked via RD, since this interferes with trouble shooting
of name servers and their databases ...
...
If recursive service is requested and available, the recursive response
to a query will be one of the following:
...
...
If recursive service is not requested or is not available, the non-
recursive response will be one of the following:
...
... depending on whether the name server is willing to provide
recursive service. If recursive service is available and
requested via the RD ...
... name server is willing to provide
recursive service. If recursive service is available and
requested via the RD bit ...
...
The DNS provides an optional service which allows name servers to
distribute, and resolvers to cache, negative results with TTLs ...
...
The resolver is located on the same machine as the program that requests
the resolver's services, but it may need to consult name servers on
other hosts. Because a resolver may need to consult several name
...
... addresses or select the "best" address if
the service returns only one choice to the client. Note that
a multiple address ...
... . This can provide an easy method of providing domain
service in a PC which lacks the resources to perform the resolver
function, or can centralize the cache ...
... database.
The user also needs to verify that the listed servers will perform the
recursive service; a name server is free to refuse to perform recursive
services for any or all ...
... recursive service; a name server is free to refuse to perform recursive
services for any or all clients. The user should consult the local
system administrator ...
... . The user should consult the local
system administrator to find name servers willing to perform the
service.
...
...
This type of service suffers from some drawbacks. Since the recursive
requests may take an arbitrary amount of time to perform, the stub may
have difficulty optimizing retransmission ...
... Dyer, S., and F. Hsu, "Hesiod", Project Athena Technical Plan - Name Service, April 1987, version 1.9.
Describes the fundamentals of the Hesiod name service ...
Describes the fundamentals of the Hesiod name service ...
... Internet Name Server", IEN-116, USC/Information Sciences Institute, August 1979.
A name service obsoleted by the Domain Name System, but still in use. ...
A name service obsoleted by the Domain Name System, but still in use. ...
... Z. Su, "A Distributed System for Internet Name Service", RFC-830, Network Information Center, SRI International, October 1982.
...
...
... NetBIOS Working Group, "Protocol standard for a NetBIOS service on a TCP/UDP transport: Concepts and Methods ...
... NetBIOS Working Group, "Protocol standard for a NetBIOS service on a TCP/UDP transport: Detailed Specifications", RFC-1002std19 ...
... Name Server", Computer Networks, vol 6, nr 3, July 1982.
Describes a name service for CSNET which is independent from the DNS and DNS use in the CSNET. ...
Describes a name service for CSNET which is independent from the DNS and DNS use in the CSNET. ...