domain
Click on the red underlined text to get to the source
...
A domain server requires a few files to get started. It will
normally have some number of boot/startup files (also known as the
"safety belt" files). One section will contain a list of possible
...
... root servers. Another section will list the zone files to be loaded
into the server for your local domain information. A zone file
typically contains all the data for a particular domain. This guide
...
... into the server for your local domain information. A zone file
typically contains all the data for a particular domain. This guide
describes the data formats that can be used in zone files and
...
... suggested parameters to use for certain fields. If you are
attempting to do anything advanced or tricky, consult the appropriate
domain RFC's for more details.
...
...
Note: Each implementation of domain software may require different
files. Zone files are standardized but some servers may require
other startup files. See the appropriate documentation that comes
...
...
A zone defines the contents of a contiguous section of the domain
space, usually bounded by administrative boundaries. There will
...
...
You may only put data in your domain server that you are
authoritative for. You must not add entries for domains other than
...
... You may only put data in your domain server that you are
authoritative for. You must not add entries for domains other than
your own (except for the special case of "glue records").
...
...
A domain server will probably read a file on start-up that lists the
zones it should load into its database ...
... zones it should load into its database. The format of this file is
not standardized and is different for most domain server
implementations. For each zone it will normally contain the domain
name of the zone and the file name that contains the data to load for
...
... not standardized and is different for most domain server
implementations. For each zone it will normally contain the domain
name of the zone and the file name that contains the data to load for
the zone.
...
... <name>
The name field defines what domain name applies to the given
RR. In some cases the name field can be left blank and it will
...
... cache the RR before it throws it out and asks a
domain server again. See the section on TTL's. If you leave
the TTL ...
...
The at-sign ("@") denotes the current default domain name.
...
...
A domain name is a sequence of labels separated by dots.
...
...
Domain names in the zone files can be one of two types, either
absolute or relative. An absolute name is the fully qualified domain
name and is terminated with a period. A relative name does not
...
... Domain names in the zone files can be one of two types, either
absolute or relative. An absolute name is the fully qualified domain
name and is terminated with a period. A relative name does not
terminate with a period, and the current default domain is appended
...
... absolute or relative. An absolute name is the fully qualified domain
name and is terminated with a period. A relative name does not
terminate with a period, and the current default domain is appended
to it. The default domain is usually the name of the domain ...
... terminate with a period, and the current default domain is appended
to it. The default domain is usually the name of the domain that was
specified in the boot file that loads each zone.
...
... domain is appended
to it. The default domain is usually the name of the domain that was
specified in the boot file that loads each zone.
...
... domain system allows a label to contain any 8-bit character.
Although the domain system has no restrictions, other protocols such
as SMTP do have name restrictions. Because of other protocol
restrictions ...
...
The domain system was designed to be protocol independent. The class
field is used to identify the protocol group ...
...
There are many defined RR types. For a complete list, see the domain
specification RFCs. Here is a list of current commonly used types.
The data for each type is described in the data section.
...
...
The NS record lists the name of a machine that provides domain
service for a particular domain ...
... domain. The name associated with the RR is
the domain name and the data portion is the name of a host that
...
... ARPA and C.ISI.EDU provide
name lookup service for the domain COM then the following entries
would be used:
...
... Note that the machines providing name service do not have to live in
the named domain. There should be one NS record for each server for
a domain ...
... domain. There should be one NS record for each server for
a domain. Also note that the name "COM" defaults for the second NS
record.
...
... NS records for a domain exist in both the zone that delegates the
domain, and in the domain itself.
...
... If the name server host for a particular domain is itself inside the
domain, then a 'glue' record will be needed. A glue record is an A
...
... host for a particular domain is itself inside the
domain, then a 'glue' record will be needed. A glue record is an A
(address) RR ...
... RR that specifies the address of the server. Glue records
are only needed in the server delegating the domain, not in the
domain itself. If for example the name server ...
... are only needed in the server delegating the domain, not in the
domain itself. If for example the name server for domain SRI.COM was
...
... domain itself. If for example the name server for domain SRI.COM was
KL.SRI.COM, then the NS record would look like this, but you will
...
...
MX records specify where mail for a domain name should be delivered.
There may be multiple MX records for a particular name. The
preference value specifies the order a mailer should try multiple MX
...
... mail to them. If they would like mail addressed to any host in the
domain FOO.COM to go through the mail gateway they might use:
...
...
The structure of names in the domain system is set up in a
hierarchical way such that the address of a name can be found by
...
... hierarchical way such that the address of a name can be found by
tracing down the domain tree contacting a server for each label of
the name. Because of this 'indexing' based on name, there is no easy
...
... RRs based on their address. This address mapping domain is called
IN-ADDR.ARPA. Within that domain ...
... domain is called
IN-ADDR.ARPA. Within that domain are subdomains for each network,
based on network ...
...
For example, the ARPANET is net 10. That means there is a domain
called 10.IN-ADDR.ARPA. Within this domain ...
...
The PTR record is used to let special names point to some other
location in the domain tree. They are mainly used in the IN-
...
... NS record for each server of the new domain to the zone
file of the parent domain.
Add any necessary glue RRs ...
...
1. Complain privately to the responsible person for the domain. You
can find their mailing address in the SOA record for the domain ...
... domain. You
can find their mailing address in the SOA record for the domain.
2. Complain publicly to the responsible person for the domain ...
... 3. Ask the NIC for the administrative person responsible for the
domain. Complain. You can also find domain contacts on the NIC in
...
... NIC for the administrative person responsible for the
domain. Complain. You can also find domain contacts on the NIC in
the file NETINFO:DOMAIN ...
... domain contacts on the NIC in
the file NETINFO:DOMAIN-CONTACTS.TXT
4. Complain to the parent domain ...
...
5. Ask the parent authorities to excommunicate the domain.
...
... The following examples show how zone files are set up for a typical
organization. SRI will be used as the example organization. SRI has
decided to divided their domain SRI.COM into a few subdomains, one
for each group that wants one. The subdomains are CSL and ISTC.
...
... All hosts at SRI are on net 128.18 except hosts in the CSL domain
which are on net 192.12.33. Note that a domain does not have to
...
... hosts in the CSL domain
which are on net 192.12.33. Note that a domain does not have to
correspond to a physical network ...
...
The examples do not necessarily correspond to actual data in use
by the SRI domain.
SRI Domain ...
... Partridge, C., "Mail Routing and the Domain System", RFC-974(-> 2821prop), CSNET CIC BBN Laboratories, January 1986. ...
... Mockapetris, P., "Domains Names - Concepts and Facilities", RFC-1034std13, USC/Information Sciences Institute, November 1987. ...
... Mockapetris, P., "Domain Names - Implementations Specification", RFC-1035std13, USC/Information Sciences Institute, November 1987. ...