1 - 4 - 7 - 8 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - Q - R - S - T - U - V - W
domain
Click on the red underlined text to get to the source
...
This RFC describes the details of the domain system and protocol, and
assumes that the reader is familiar with the concepts discussed in a
companion RFC, "Domain Names ...
... domain system and protocol, and
assumes that the reader is familiar with the concepts discussed in a
companion RFC, "Domain Names - Concepts and Facilities" [RFC-1034].
...
...
The domain system is a mixture of functions and data types which are an
official protocol and functions and data types which are still
experimental. Since the ...
... system is a mixture of functions and data types which are an
official protocol and functions and data types which are still
experimental. Since the domain system is intentionally extensible, new
data types and experimental behavior should always be expected in parts
...
...
The goal of domain names is to provide a mechanism for naming resources
in such a way that the names are usable in different hosts, networks ...
...
From the user's point of view, domain names are useful as arguments to a
local agent, called a resolver, which retrieves information associated
...
... local agent, called a resolver, which retrieves information associated
with the domain name. Thus a user might ask for the host address or
...
... host address or
mail information associated with a particular domain name. To enable
the user to request a particular type of information, an appropriate
query type is passed to the resolver with the ...
... . To enable
the user to request a particular type of information, an appropriate
query type is passed to the resolver with the domain name. To the user,
the domain tree ...
... query type is passed to the resolver with the domain name. To the user,
the domain tree is a single information space; the resolver is
responsible for hiding the distribution of data among name servers from
...
...
From the resolver's point of view, the database that makes up the domain
space is distributed among various name servers. Different parts of the
domain space are stored in different name servers, although a ...
... that makes up the domain
space is distributed among various name servers. Different parts of the
domain space are stored in different name servers, although a particular
data item will be stored redundantly in two or more name servers. The
resolver starts ...
... referrals, resolvers learn the identities and contents of other name
servers. Resolvers are responsible for dealing with the distribution of
the domain space and dealing with the effects of name server failure by
consulting redundant databases ...
... database for a particular
"pruned" subtree of the domain space. This data is called
authoritative. A name server periodically checks to make sure that its
...
...
A host can participate in the domain name system in a number of ways,
depending on whether the host runs programs that retrieve information
...
... depending on whether the host runs programs that retrieve information
from the domain system, name servers that answer queries from other
hosts, or various combinations of both functions. The simplest, and
...
...
User programs interact with the domain name space through resolvers; the
format of user queries and user responses is specific to the host ...
... The information flow in a host that supports all aspects of the domain
name system is shown below:
...
...
The shared database holds domain space data for the local name server
and resolver. The contents of the shared database ...
... operations of the name server and cached data from previous resolver
requests. The structure of the domain data and the necessity for
synchronization between name servers and resolvers imply the general
characteristics of this ...
...
In any case, note that domain components are always replicated for
reliability whenever possible.
...
...
The domain system has several conventions dealing with low-level, but
fundamental, issues. While the implementor ...
... The DNS specifications attempt to be as general as possible in the rules
for constructing domain names. The idea is that the name of any
existing object can be expressed as a domain name with minimal changes.
...
... for constructing domain names. The idea is that the name of any
existing object can be expressed as a domain name with minimal changes.
...
...
However, when assigning a domain name for an object, the prudent user
will select a name which satisfies both the rules of the domain system
...
... However, when assigning a domain name for an object, the prudent user
will select a name which satisfies both the rules of the domain system
and any existing rules for the object, whether these rules are published
or implied by existing programs.
...
...
For example, when naming a mail domain, the user should satisfy both the
rules of this memo and those in RFC-822std11(-> 2822prop). When creating a new host name ...
... the old rules for HOSTS.TXT should be followed. This avoids problems
when old software is converted to use domain names.
...
...
The following syntax will result in fewer problems with many
applications that use domain names (e.g., mail, TELNET).
...
...
Note that while upper and lower case letters are allowed in domain
names, no significance is attached to the case. That is, two names with
the same spelling but different case are to be treated as if identical.
...
... For all parts of the DNS that are part of the official protocol, all
comparisons between character strings (e.g., labels, domain names, etc.)
are done in a case-insensitive manner. At present, this rule is in
...
... are done in a case-insensitive manner. At present, this rule is in
force throughout the domain system without exception. However, future
additions beyond current usage may need to use the full binary octet
capabilities in names, so attempts to store domain names ...
... domain system without exception. However, future
additions beyond current usage may need to use the full binary octet
capabilities in names, so attempts to store domain names in 7-bit ASCII
...
...
When data enters the domain system, its original case should be
preserved whenever possible. In certain circumstances this cannot be
done. For example, if two RRs ...
... and X.Y may both be stored under a single location x.y or X.Y, data for
a.x and B.X would never be stored under A.x, A.X, b.x, or b.X. In
general, this preserves the case of the first label of a domain name,
but forces standardization of interior node ...
...
Systems administrators who enter data into the domain database should
take care to represent the data they supply to the domain ...
... domain database should
take care to represent the data they supply to the domain system in a
case-consistent manner if their system is case-sensitive. The data
distribution system in the ...
... system in a
case-consistent manner if their system is case-sensitive. The data
distribution system in the domain system will ensure that consistent
representations are preserved.
...
... DOMAIN NAME SPACE AND RR DEFINITIONS ...
...
Domain names in messages are expressed in terms of a sequence of labels.
Each label is represented as a one octet length field followed by that
number of octets. Since every domain name ...
... Domain names in messages are expressed in terms of a sequence of labels.
Each label is represented as a one octet length field followed by that
number of octets. Since every domain name ends with the null label of
the root, a domain name ...
... domain name ends with the null label of
the root, a domain name is terminated by a length byte of zero. The
high order two bits of every length octet must be zero, and the
...
...
To simplify implementations, the total length of a domain name (i.e.,
label octets and label length octets) is restricted to 255 octets or
less.
...
... 9 a mail rename domain name (EXPERIMENTAL) ...
... 12 a domain name pointer ...
... classes.
Because their RDATA format is known, all domain names in the RDATA
section of these RRs ...
...
<domain-name> is a domain name represented as a series of labels, and
terminated by a label with zero length. <character-string> is a single
...
...
<domain-name> is a domain name represented as a series of labels, and
terminated by a label with zero length. <character-string> is a single
length octet followed by that number of characters. <character-string>
...
... A <domain-name> which specifies the canonical or primary
name for the owner. The owner name is an alias ...
... host which has a mail
agent for the domain which should be able to deliver
mail for the domain. ...
... host which has a mail
agent for the domain which will accept mail for
forwarding to the domain. ...
... RR (similar
to the ERRORS-TO: field which has been proposed). If
this domain name names the root, errors should be
returned to the sender ...
... A <domain-name> which specifies a mailbox which is the
proper rename of the specified mailbox ...
... A <domain-name> which specifies a host willing to act as
a mail exchange for the owner name.
...
... A <domain-name> which specifies a host which should be
authoritative for the specified class ...
... A <domain-name> which points to some location in the
domain name space. ...
... A <domain-name> which points to some location in the
domain name space. ...
... PTR records cause no additional section processing. These RRs are used
in special domains to point to some other location in the domain space.
These records are simple data, and don't imply any special processing
...
... RRs are used
in special domains to point to some other location in the domain space.
These records are simple data, and don't imply any special processing
similar to that performed by CNAME ...
... The <domain-name> of the name server that was the
original or primary source of data for this zone. ...
... RRs are used to hold descriptive text. The semantics of the text
depends on the domain where it is found.
...
... IN-ADDR.ARPA domain ...
... host mapping. Other classes may employ a similar
strategy in other domains. The intent of this domain is to provide a
guaranteed method ...
... classes may employ a similar
strategy in other domains. The intent of this domain is to provide a
guaranteed method to perform host ...
... are similar to functions that could be
performed by inverse queries; the difference is that this part of the
domain name space is structured according to address, and hence can
guarantee that the appropriate data can be located without an exhaustive
...
... , and hence can
guarantee that the appropriate data can be located without an exhaustive
search of the domain space.
...
...
Domain names in the IN-ADDR.ARPA domain are defined to have up to four
labels in addition to the IN-ADDR.ARPA suffix ...
...
Host addresses are represented by domain names that have all four labels
specified. Thus data for Internet address 10.2.0.52 is located at
...
... that have all four labels
specified. Thus data for Internet address 10.2.0.52 is located at
domain name 52.0.2.10.IN-ADDR.ARPA. The reversal, though awkward to
...
... nodes at various depths
in the IN-ADDR.ARPA domain, since Internet network numbers are either 1,
2, or 3 octets. Network ...
... address nodes use the PTR RR to point back to the primary domain
names of the corresponding hosts.
...
...
For example, the IN-ADDR.ARPA domain will contain information about the
ISI gateway between net 10 and 26, an MIT ...
... addresses 10.0.0.77 and 18.10.0.4
and a name GW.LCS.MIT.EDU, the domain database would contain:
...
... Since the IN-ADDR.ARPA special domain and the normal domain
for a particular host or gateway ...
... , or when a copy of the existing
name space is desired, but a separate management domain is necessary.
...
... . Thus, in order to find the
address of the host for a mail exchange, you map the mail domain name to
a host name, then the host name ...
...
All communications inside of the domain protocol are carried in a single
format called a message. The top level format of message is divided
...
... query class (QCLASS), and a query domain name (QNAME). The last three
sections have the same format: a possibly empty list of concatenated
resource records ( ...
... responses from an authoritative name
server, this code signifies that the
domain name referenced in the query does
not exist. ...
... a domain name represented as a sequence of labels, where
each label consists of a length octet followed by that
number of octets. The domain name ...
... domain name represented as a sequence of labels, where
each label consists of a length octet followed by that
number of octets. The domain name terminates with the
zero length octet for the null label of the root. Note
...
... a domain name to which this resource record pertains. ...
...
In order to reduce the size of messages, the domain system utilizes a
compression scheme which eliminates the repetition of domain names in a
...
... In order to reduce the size of messages, the domain system utilizes a
compression scheme which eliminates the repetition of domain names in a
message. In this scheme, an entire domain name or a list of labels at
...
... compression scheme which eliminates the repetition of domain names in a
message. In this scheme, an entire domain name or a list of labels at
the end of a domain name is replaced with a pointer to a prior occurance
...
... message. In this scheme, an entire domain name or a list of labels at
the end of a domain name is replaced with a pointer to a prior occurance
of the same name.
...
... specifies an offset from
the start of the message (i.e., the first octet of the ID field in the
domain header). A zero offset specifies the first byte of the ID field,
etc.
...
...
The compression scheme allows a domain name in a message to be
represented as either:
...
...
Pointers can only be used for occurances of a domain name where the
format is not class specific. If this were not the case, a name server ...
...
If a domain name is contained in a part of the message subject to a
length field (such as the RDATA ...
... ARPA, and the root. Ignoring the other fields of the
message, these domain names might be represented as:
...
... The domain name for F.ISI.ARPA is shown at offset 20. The domain name
FOO.F.ISI.ARPA is shown at offset 40; this definition uses a pointer to
...
... is shown at offset 40; this definition uses a pointer to
concatenate a label for FOO to the previously defined F.ISI.ARPA. The
domain name ARPA is defined at offset 64 using a pointer to the ARPA
...
... component of the name F.ISI.ARPA at 20; note that this pointer relies on
ARPA being the last label in the string at 20. The root domain name is
defined by a single octet of zeros at 92; the root domain name has no
...
... ARPA being the last label in the string at 20. The root domain name is
defined by a single octet of zeros at 92; the root domain name has no
labels.
...
... ORIGIN and $INCLUDE. $ORIGIN is
followed by a domain name, and resets the current origin for relative
domain names to the stated name. $INCLUDE inserts the named file into
the current file, and may optionally specify a ...
... is
followed by a domain name, and resets the current origin for relative
domain names to the stated name. $INCLUDE inserts the named file into
the current file, and may optionally specify a domain name that sets the
...
... , and resets the current origin for relative
domain names to the stated name. $INCLUDE inserts the named file into
the current file, and may optionally specify a domain name that sets the
relative domain name origin for the included file. $INCLUDE may also
...
... the current file, and may optionally specify a domain name that sets the
relative domain name origin for the included file. $INCLUDE may also
have a comment. Note that a $INCLUDE entry never changes the relative
origin of the parent file, regardless of changes to the relative origin
...
... RR is assumed to be owned by the last stated owner. If
an RR entry begins with a <domain-name>, then the owner name is reset.
...
...
<domain-name>s make up a large share of the data in the master file.
The labels in the domain name are expressed as character strings and
...
... <domain-name>s make up a large share of the data in the master file.
The labels in the domain name are expressed as character strings and
separated by dots. Quoting conventions allow arbitrary characters to be
stored in domain names ...
... domain name are expressed as character strings and
separated by dots. Quoting conventions allow arbitrary characters to be
stored in domain names. Domain names that end in a dot are called
absolute, and are taken as complete. Domain names ...
... separated by dots. Quoting conventions allow arbitrary characters to be
stored in domain names. Domain names that end in a dot are called
absolute, and are taken as complete. Domain names which do not end in a
...
... domain names. Domain names that end in a dot are called
absolute, and are taken as complete. Domain names which do not end in a
dot are called relative; the actual domain name is the concatenation ...
... absolute, and are taken as complete. Domain names which do not end in a
dot are called relative; the actual domain name is the concatenation of
the relative part with an origin specified in a $ORIGIN ...
... query operations;
while a standard query maps a domain name to a resource, an inverse
query maps a resource to a domain name. For example, a standard ...
... maps a domain name to a resource, an inverse
query maps a resource to a domain name. For example, a standard query
might bind a domain name ...
... domain name. For example, a standard query
might bind a domain name to a host address; the corresponding inverse
...
... NAME SERVER KNOWS. Since no name server knows
about all of the domain name space, the response can never be assumed to
be complete. Thus inverse queries are primarily useful for database ...
... zero, one, or multiple domain names for the specified
resource as QNAMEs in the question section ...
... The overall structure
of an inverse query for retrieving the domain name that corresponds to
Internet address 10.1.0.52 is shown below:
...
... asks for a question whose answer is the Internet style
address 10.1.0.52. Since the owner name is not known, any domain name
can be used as a placeholder (and is ignored). A single octet of zero,
signifying the root ...
...
Support for transfer of this type of inversion may be included in future
versions of the domain system, but is not supported in this version.
...
... The next step is to match the response to a current resolver request.
The recommended strategy is to do a preliminary matching using the ID
field in the domain header, and then to verify that the question section
corresponds to the information currently desired. This requires that
...
... the transmission algorithm devote several bits of the domain ID field to
a request identifier of some sort. This step has several fine points:
...
...
The domain system defines a standard for mapping mailboxes into domain
names, and two methods ...
... The domain system defines a standard for mapping mailboxes into domain
names, and two methods for using the mailbox information to derive mail
routing ...
... encoding standard assumes a mailbox name of the form
"<local-part>@<mail-domain>". While the syntax allowed in each of these
sections varies substantially between the various mail internets, the
preferred syntax for the ARPA ...
... The DNS encodes the <local-part> as a single label, and encodes the
<mail-domain> as a domain name. The single label from the <local-part>
is prefaced to the domain name ...
... DNS encodes the <local-part> as a single label, and encodes the
<mail-domain> as a domain name. The single label from the <local-part>
is prefaced to the domain name from <mail-domain ...
... domain> as a domain name. The single label from the <local-part>
is prefaced to the domain name from <mail-domain> to form the domain
name corresponding to the mailbox ...
... domain name. The single label from the <local-part>
is prefaced to the domain name from <mail-domain> to form the domain
name corresponding to the mailbox. Thus the mailbox ...
... is prefaced to the domain name from <mail-domain> to form the domain
name corresponding to the mailbox. Thus the mailbox HOSTMASTER@SRI-
...
... <local-part> contains dots or other special characters, its
representation in a master file will require the use of backslash
quoting to ensure that the domain name is properly encoded. For
example, the mailbox Action.domains ...
... domain name is properly encoded. For
example, the mailbox Action.domains@ISI.EDU would be represented as
Action\.domains.ISI.EDU.
...
...
Mail exchange binding uses the <mail-domain> part of a mailbox
specification to determine where mail should be sent. The <local-part>
...
...
The essence of the method is that the <mail-domain> is used as a domain
name to locate type MX RRs which list hosts ...
... The essence of the method is that the <mail-domain> is used as a domain
name to locate type MX RRs which list hosts willing to accept mail for
...
... RRs which list hosts willing to accept mail for
<mail-domain>, together with preference values which rank the hosts
according to an order specified by the administrators ...
...
In this memo, the <mail-domain> ISI.EDU is used in examples, together
with the hosts VENERA.ISI.EDU and VAXA.ISI.EDU as mail exchanges for
...
... binding, the mailer uses the entire mail destination
specification to construct a domain name. The encoded domain name for
the mailbox ...
... destination
specification to construct a domain name. The encoded domain name for
the mailbox is used as the QNAME field in a QTYPE=MAILB query ...
... 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. ...
... D. Mills, "Internet Name Domains", RFC-799, COMSAT, September 1981.
Suggests introduction of a hierarchy in place of a flat name space ...
Suggests introduction of a hierarchy in place of a flat name space ...
... Z. Su, and J. Postel, "The Domain Naming Convention for Internet User Applications", RFC-819, Network ...
... 819, Network Information Center, SRI International, August 1982.
Early thoughts on the design of the domain system. Current implementation is completely different. ...
Early thoughts on the design of the domain system. Current implementation is completely different. ...
... 830, Network Information Center, SRI International, October 1982.
Early thoughts on the design of the domain system. Current implementation is completely different. ...
Early thoughts on the design of the domain system. Current implementation is completely different. ...
... P. Mockapetris, "Domain names - Concepts and Facilities," RFC-882(-> 1035std13 | 1034std13), USC/Information Sciences Institute, November 1983. Superceeded by this memo. ...
... P. Mockapetris, "Domain names - Implementation and Specification," RFC-883(-> 1035std13 | 1034std13), USC/Information Sciences Institute, November 1983. Superceeded by this memo. ...
... J. Postel and J. Reynolds, "Domain Requirements", RFC-920, USC/Information Sciences Institute, October 1984. Explains the naming scheme for top level domains ...
... Domain Requirements", RFC-920, USC/Information Sciences Institute, October 1984. Explains the naming scheme for top level domains. ...
... P. Mockapetris, "Domain System Changes and Observations", RFC-973(-> 1035std13 | 1034std13), USC/Information Sciences Institute, January 1986.
Describes changes to RFC-882(-> 1035std13 | 1034std13) ...
Describes changes to RFC-882(-> 1035std13 | 1034std13) ...
... C. Partridge, "Mail routing and the domain system", RFC-974(-> 2821prop), CSNET CIC BBN Labs, January 1986.
Describes the transition from HOSTS ...
Describes the transition from HOSTS ...
...
Describes the transition from HOSTS.TXT based mail addressing to the more powerful MX system used with the domain system. ...
Describes the transition from HOSTS.TXT based mail addressing to the more powerful MX system used with the domain system. ...
... W. Lazear, "MILNET Name Domain Transition", RFC-1031, November 1987. Describes a plan for converting the MILNET to the DNS. ...
... registration policies used by the NIC to administer the top level domains and delegate subzones. ...
... M. Lottor, "Domain Administrators Operations Guide", RFC-1033, November 1987. A cookbook for domain ...
... Domain Administrators Operations Guide", RFC-1033, November 1987. A cookbook for domain administrators. ...