os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Structural Markup Changes to DNS:

Browse source 
* Terminology -> <informaltable>
* File list -> <informaltable>
* Record Types -> <variablelist>
* Links -> <itemizedlist>

Reviewed by:	murray
This commit is contained in:
Chern Lee 2001-08-06 20:25:01 +00:00
parent 565a2b3a46
commit 2ed036cc7c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10208
1 changed files with 213 additions and 102 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

315
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.66 2001/08/02 01:57:08 chern Exp $
$FreeBSD$
-->
<chapter id="advanced-networking">
@ -3006,10 +3006,68 @@ dhcp_flags=""</programlisting>
<para>To understand this document, some terms related to DNS must be
understood.</para>
<indexterm><primary>zones</primary></indexterm>
<para><emphasis>zone</emphasis> - Each individual domain, subdomain,
or area dictated by DNS
</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>Term</entry>
<entry>Definition</entry>
</row>
</thead>
<tbody>
<row>
<entry>forward dns</entry>
<entry>mapping of hostnames to IP addresses</entry>
</row>
<row>
<entry>origin</entry>
<entry>refers to the point of start for the particular zone</entry>
</row>
<row>
<entry>named, bind, name server</entry>
<entry>common names for the BIND name server package within
FreeBSD</entry>
</row>
<indexterm><primary>resolver</primary></indexterm>
<row>
<entry>resolver</entry>
<entry>a system process through which a
machine queries a nameserver for zone information</entry>
</row>
<indexterm><primary>reverse dns</primary></indexterm>
<row>
<entry>reverse DNS</entry>
<entry>the opposite of forward DNS, mapping of IP addresses to
hostnames</entry>
</row>
<indexterm><primary>root zone</primary></indexterm>
<row>
<entry>root zone</entry>
<entry>literally, a <quote>.</quote>, refers to the
root, or beginning zone. All zones fall under this, as
do all files in fall under the root directory. It is
the beginning of the Internet zone hierarchy.</entry>
</row>
<row>
<entry>zone</entry>
<entry>Each individual domain, subdomain, or area dictated by
DNS</entry>
</tbody>
</tgroup>
</informaltable>
<indexterm>
<primary>zones</primary>
<secondary>examples</secondary>
</indexterm>
<para>Examples of zones:
</para>
@ -3043,34 +3101,7 @@ dhcp_flags=""</programlisting>
a hostname is much like a filesystem: the <filename>/dev</filename>
directory falls within the root, and so on.</para>
<para><emphasis>named, bind, name server</emphasis> - these are all
common names for the BIND name server package within FreeBSD.
</para>
<indexterm><primary>resolver</primary></indexterm>
<para><emphasis>resolver</emphasis> - a system process through which a
machine queries a nameserver for zone information
</para>
<indexterm><primary>root zone</primary></indexterm>
<para><emphasis>root zone</emphasis> - literally, a '.', refers to
the root, or beginning zone. All zones fall under this, as do all
files in fall under the root directory. It is the beginning of the
Internet zone hierarchy.
</para>
<para><emphasis>origin</emphasis> - refers to the point of start for
the particular zone
</para>
<para><emphasis>forward dns</emphasis> - mapping of hostnames to IP
addresses
</para>
<indexterm><primary>reverse DNS</primary></indexterm>
<para><emphasis>reverse dns</emphasis> - the opposite of forward DNS,
mapping of IP addresses to hostnames
</para>
</sect2>
<sect2>
@ -3145,20 +3176,41 @@ dhcp_flags=""</programlisting>
<para>In FreeBSD, the BIND daemon is called
<application>named</application> for obvious reasons.</para>
<para><command>named</command> - the bind daemon</para>
<para><command>ndc</command> - name daemon control program</para>
<informaltable frame="none">
<tgroup cols="2">
<thead>
<row>
<entry>File</entry>
<entry>Description</entry>
</row>
</thead>
<tbody>
<row>
<entry><application>named</application></entry>
<entry>the BIND daemon</entry>
</row>
<row>
<entry><command>ndc</command></entry>
<entry>name daemon control program</entry>
</row>
<row>
<entry><filename>/etc/namedb</filename></entry>
<entry>directory where BIND zone information resides</entry>
</row>
<row>
<entry><filename>/etc/namedb/named.conf</filename></entry>
<entry>daemon configuration file</entry>
</row>
</tbody>
</tgroup>
</informaltable>
<para>
<filename>/etc/namedb</filename> - directory where BIND zone
information resides
</para>
<para>
<filename>/etc/namedb/named.conf</filename> - daemon configuration
file
</para>
<para>
zone files are usually contained within the
Zone files are usually contained within the
<filename>/etc/namedb</filename>
directory, and contain the DNS zone information
served by the name server.
@ -3430,14 +3482,45 @@ www IN CNAME @
<para>
The most commonly used DNS records:
</para>
<para><varname>SOA</varname> - start of zone authority</para>
<para><varname>NS</varname> - an authoritative nameserver</para>
<para><varname>A</varname> - A host address</para>
<para><varname>CNAME</varname> - the canonical name for an
alias</para>
<para><varname>MX</varname> - mail exchange</para>
<para><varname>PTR</varname> - a domain name pointer (used in
reverse dns)</para>
<variablelist>
<varlistentry>
<term>SOA</term>
<listitem><para>start of zone authority</para></listitem>
</varlistentry>
<varlistentry>
<term>NS</term>
<listitem><para>an authoritative nameserver</para></listitem>
</varlistentry>
<varlistentry>
<term>A</term>
<listitem><para>A host address</para></listitem>
</varlistentry>
<varlistentry>
<term>CNAME</term>
<listitem><para>the canonical name for an alias</para></listitem>
</varlistentry>
<varlistentry>
<term>MX</term>
<listitem><para>mail exchange</para></listitem>
</varlistentry>
<varlistentry>
<term>PTR</term>
<listitem><para>a domain name pointer (used in reverse dns)
</para></listitem>
</varlistentry>
</variablelist>
<programlisting>
foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. (
@ -3447,29 +3530,48 @@ foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. (
604800 ; Expire after 1 week
86400 ) ; Minimum TTL of 1 day</programlisting>
<para>
<hostid>foobardomain.org.</hostid> - the domain name, also
the origin for this zone file.
</para>
<para><hostid>ns1.foobardomain.org.</hostid> - the
primary/authoritative nameserver for this zone
</para>
<para><email>admin.foobardomain.org.</email> - the
responsible person for this zone, email address with @
<variablelist>
<varlistentry>
<term><hostid>foobardomain.org.</hostid></term>
<listitem><para>the domain name, also the origin for this
zone file.</para></listitem>
</varlistentry>
<varlistentry>
<term><hostid>ns1.foobardomain.org.</hostid></term>
<listitem><para>the primary/authoritative nameserver for this
zone</para></listitem>
</varlistentry>
<varlistentry>
<term><literal>admin.foobardomain.org.</literal></term>
<listitem><para>the responsible person for this zone,
email address with @
replaced. (<email>admin@foobardomain.org</email> becomes
<email>admin.foobardomain.org</email>)
</para>
<para>
<emphasis>5</emphasis> - the serial number of the file. this
must
be incremented each time the zone file is modified. Nowadays,
many admins prefer a <literal>yyyymmddrr</literal> format for the serial
number.
2001041002 would mean last modified 04/10/2001, the latter 02 being
the second time the zone file has been modified this day. The
serial number is important as it alerts slave nameservers for a zone
when it is updated.
</para>
<literal>admin.foobardomain.org</literal>)</para>
</listitem>
</varlistentry>
<varlistentry>
<term><literal>5</literal>
<listitem><para>the serial number of the file. this
must be incremented each time the zone file is modified.
Nowadays, many admins prefer a
<literal>yyyymmddrr</literal> format for the serial
number. 2001041002 would mean last modified 04/10/2001,
the latter 02 being the second time the zone file has
been modified this day. The serial number is important
as it alerts slave nameservers for a zone when it is
updated.</para>
</listitem>
</varlistentry>
</variablelist>
<programlisting>
@ IN NS ns1.foobardomain.org.</programlisting>
@ -3491,9 +3593,10 @@ mail IN A 3.2.1.10
<para>
The A record indicates machine names. As seen above,
ns1.foobardomain.org would resolve to 3.2.1.2. Again, the
origin symbol, <literal>@</literal>, is used here, thus meaning
foobardomain.org would resolve to <hostid>3.2.1.30</hostid>.
<hostid>ns1.foobardomain.org</hostid> would resolve to
3.2.1.2. Again, the origin symbol, <literal>@</literal>, is
used here, thus meaning <hostid>foobardomain.org</hostid>
would resolve to <hostid>3.2.1.30</hostid>.
</para>
<programlisting>
@ -3501,10 +3604,12 @@ www IN CNAME @</programlisting>
<para>
The canonical name record is usually used for giving aliases
to a machine. In the example, www is aliased to the machine
addressed to the origin, or foobardomain.org (3.2.1.30).
<varname>CNAME</varname>s can be used to provide alias hostnames, or round
robin one hostname among multiple machines.
to a machine. In the example, <hostid>www</hostid> is
aliased to the machine addressed to the origin, or
<hostid>foobardomain.org</hostid> (3.2.1.30).
<varname>CNAME</varname>s can be used to provide alias
hostnames, or round robin one hostname among multiple
machines.
</para>
<programlisting>
@ -3711,33 +3816,39 @@ www IN CNAME @</programlisting>
<sect2>
<title>Further Reading</title>
<para>
&man.ndc.8; &man.named.8; &man.named.conf.5;
BIND/named man pages: &man.ndc.8; &man.named.8; &man.named.conf.5;
</para>
<para>
Official ISC BIND Page
<ulink url="http://www.isc.org/products/BIND/">http://www.isc.org/products/BIND/</ulink>
</para>
<itemizedlist>
<listitem>
<para><ulink
url="http://www.isc.org/products/BIND/">Official ISC Bind
Page</ulink></para>
</listitem>
<para>
BIND FAQ
<ulink url="http://www.nominum.com/resources/faqs/bind-faqs.html">
http://www.nominum.com/resources/faqs/bind-faqs.html</ulink>
</para>
<listitem>
<para><ulink
url="http://www.nominum.com/resources/faqs/bind-faqs.html">
BIND FAQ</ulink></para>
</listitem>
<para>
<ulink url="http://www.oreilly.com/catalog/dns4/">O'Reilly DNS and BIND 4th Edition</ulink>
</para>
<listitem>
<para><ulink url="http://www.oreilly.com/catalog/dns4/">O'Reilly
DNS and BIND 4th Edition</ulink></para>
</listitem>
<para>
<ulink url="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1034.txt">RFC1034 - Domain Names -
Concepts and Facilities</ulink>
</para>
<listitem>
<para><ulink
url="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1034.txt">RFC1034
- Domain Names - Concepts and Facilities</ulink></para>
</listitem>
<para>
<ulink url="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1035.txt">RFC1035 - Domain Names -
Implementation and Specification</ulink>
</para>
<listitem>
<para><ulink
url="http://info.internet.isi.edu:80/in-notes/rfc/files/rfc1035.txt">RFC1035
- Domain Names - Implementation and Specification</ulink></para>
</listitem>
</itemizedlist>
</sect2>
</sect1>