domain name
Click on the red underlined text to get to the source
...
This RFC is an introduction to the Domain Name System (DNS), and omits
many details which can be found in a companion RFC, "Domain Names ...
... Domain Name System (DNS), and omits
many details which can be found in a companion RFC, "Domain Names -
Implementation and Specification" [RFC-1035std13]. That RFC assumes that the
...
... host address support, and the protocols and servers used to implement
domain name facilities.
...
... The history of domain names ...
...
The terms "domain" or "domain name" are used in many contexts beyond the
DNS described here. Very often, the term ...
... " are used in many contexts beyond the
DNS described here. Very often, the term domain name is used to refer
to a name with structure indicated by dots, but no relation to the DNS.
...
... associated with the names. Conceptually, each node and leaf
of the domain name space tree names a set of information, and
query ...
... query operations are attempts to extract specific types of
information from a particular set. A query names the domain
name of interest and describes the type of resource
information that is desired. For example, the Internet
...
... information that is desired. For example, the Internet
uses some of its domain names to identify hosts; queries for
...
... DOMAIN NAME SPACE and RESOURCE RECORDS ...
... to the root of the tree. By convention, the labels that compose a
domain name are printed or read left to right, from the most specific
(lowest, farthest from the root) to the least specific (highest, closest
...
...
Internally, programs that manipulate domain names should represent them
as sequences of labels, where each label is a length octet followed by
an octet string. Because all domain ...
... root, which has a
null string for a label, these internal representations can use a length
byte of zero to terminate a domain name.
...
...
By convention, domain names can be stored with arbitrary case, but
domain name comparisons for all present domain functions are done in a
...
...
By convention, domain names can be stored with arbitrary case, but
domain name comparisons for all present domain functions are done in a
case-insensitive manner, assuming an ...
... label "A" or a node with label "a", but not both as brothers; you could
refer to either using "a" or "A". When you receive a domain name or
label, you should preserve its case. The rationale for this choice is
that we may someday need to add full binary domain names ...
... domain name or
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.
...
...
When a user needs to type a domain name, the length of each label is
omitted and the labels are separated by dots ("."). Since a complete
domain name ends with the ...
... When a user needs to type a domain name, the length of each label is
omitted and the labels are separated by dots ("."). Since a complete
domain name ends with the root label, this leads to a printed form which
ends in a dot. We use this property to distinguish between:
...
... a character string which represents a complete domain name
(often called "absolute"). For example, "poneria.ISI.EDU."
...
... a character string that represents the starting labels of a
domain name which is incomplete, and should be completed by
local software using knowledge of the local domain (often
...
... user interface, where their interpretation varies from
implementation to implementation, and in master files, where they are
relative to a single origin domain name. The most common interpretation
uses the root "." as either the single origin or as one of the members
...
...
To simplify implementations, the total number of octets that represent a
domain name (i.e., the sum of all label octets and label lengths) is
limited to 255.
...
...
A domain is identified by a domain name, and consists of that part of
the domain name space that is at or below the domain name ...
... domain is identified by a domain name, and consists of that part of
the domain name space that is at or below the domain name which
specifies the domain ...
... domain name, and consists of that part of
the domain name space that is at or below the domain name which
specifies the domain. A domain ...
... A convention for mapping between object names and domain
names. This describes how information about an object is
accessed.
...
... hosts, the mapping depends on the existing syntax for host names
which is a subset of the usual text representation for domain names,
together with RR formats for describing host ...
... , the mapping is slightly more complex. The usual mail
address <local-part>@<mail-domain> is mapped into a domain name by
converting <local-part> into a single label (regardles of dots it
contains), converting <mail-domain ...
... converting <local-part> into a single label (regardles of dots it
contains), converting <mail-domain> into a domain name using the usual
text format for domain names (dots denote label breaks), and
...
... domain> into a domain name using the usual
text format for domain names (dots denote label breaks), and
concatenating the two to form a single domain name. Thus the mailbox ...
...
The following figure shows a part of the current domain name space, and
is used in many examples in this RFC. Note that the tree is a very
...
... 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
...
... 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.
...
... which is the domain name where the RR is found. ...
... a pointer to another part of the domain name space ...
... a domain name. ...
... a domain name. ...
... RDATA section of RRs is carried as a combination of
binary strings and domain names. The domain names are frequently used
as "pointers" to other data in the DNS ...
... RRs is carried as a combination of
binary strings and domain names. The domain names are frequently used
as "pointers" to other data in the DNS.
...
... RDATA section which consists of a 16 bit number
followed by a domain name. The address RRs use a standard IP address ...
...
fails to find a desired RR in the resource set associated with the
domain name, it checks to see if the resource set consists of a CNAME
record with a matching class ...
... record in the response and restarts the query at the domain name
specified in the data field of the CNAME ...
...
Domain names in RRs which point at another name should always point at
the primary name and not the alias ...
... name server that does; a name server
that returns a domain name in a relevant RR may also return the RR that
...
... Name servers may also support inverse queries that map a particular
resource to a domain name or domain names that have that resource. For
example, while a standard query ...
... queries that map a particular
resource to a domain name or domain names that have that resource. For
example, while a standard query might map a domain name ...
... domain names that have that resource. For
example, while a standard query might map a domain name to a SOA RR, the
corresponding inverse query ...
... inverse queries because the domain system is organized by domain name
rather than by host address ...
...
These rules mean that every zone has at least one node, and hence domain
name, for which it is authoritative, and all of the nodes in a
particular zone are connected. Given, the tree structure ...
... It would be possible, though not particularly useful, to partition the
name space so that each domain name was in a separate zone or so that
all nodes were in a single zone. Instead, the database ...
... wildcard RRs is of
the form "*.<anydomain>", where <anydomain> is any domain name.
<anydomain> should not contain other * labels, and should be in the
authoritative data of the zone. The wildcards ...
...
This would cause any MX query for any domain name ending in X.COM to
return an MX RR pointing at A.X.COM. Two wildcard ...
...
Resolvers are programs that interface user programs to domain name
servers. In the simplest case, a resolver receives a request from a
user program (e.g., mail programs, TELNET ...
... the domain name we are searching for. ...
... RRs,
starting at SNAME, then the parent domain name of SNAME, the
grandparent, and so on toward the root. Thus if SNAME were
...
... name server RR contents.
Relative and absolute domain names may be freely intermixed in a master
...
... Suppose the first request to the resolver comes from the local mailer,
which has mail for PVM@ISI.EDU. The mailer might then ask for type MX
RRs for the domain name ISI.EDU.
...
... 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. ...
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. ...