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 name
Click on the red underlined text to get to the source
... 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 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 ...
...
A host can participate in the domain name system in a number of ways,
depending on whether the host runs programs that retrieve information
...
...
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 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
...
... 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
...
... 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
...
... 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 ...
... 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 ...
...
<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>
...
... 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 points to some location in the
domain name space. ...
... 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
...
...
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
...
... address nodes use the PTR RR to point back to the primary domain
names of the corresponding hosts.
...
... . 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 ...
... 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
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.
...
...
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
...
... 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
...
... <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 ...
... The domain system defines a standard for mapping mailboxes into domain
names, and two methods for using the mailbox information to derive mail
routing ...
... 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 ...
... 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 ...
... 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
...
... 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. ...
... 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. ...