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

s/foobardomain/foobar/

Browse source 
Example domain names that are used inline should be kept as short as
possible.  Domain names can not be broken up with hyphenation at
syllable boundaries for obvious reasons, and using 12 unbreakable
characters is bound to cause an hbox overflow when creating justified
output with TeX (the print backend).
This commit is contained in:
Murray Stokely 2001-10-16 18:49:55 +00:00
parent 49731ee7b9
commit 4c5f65dfb8
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10958
1 changed files with 41 additions and 41 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -3564,11 +3564,11 @@ dhcp_flags=""</programlisting>
<para><hostid>org.</hostid> is a zone under the root zone</para> <para><hostid>org.</hostid> is a zone under the root zone</para>
</listitem> </listitem>
<listitem> <listitem>
<para><hostid>foobardomain.org</hostid> is a zone under the org. zone</para> <para><hostid>foobar.org</hostid> is a zone under the org. zone</para>
</listitem> </listitem>
<listitem> <listitem>
<para><hostid>foo.foobardomain.org.</hostid> is a subdomain, a zone under the <para><hostid>foo.foobar.org.</hostid> is a subdomain, a zone under the
<hostid>foobardomain.org.</hostid> zone <hostid>foobar.org.</hostid> zone
</para> </para>
</listitem> </listitem>
<listitem> <listitem>
@ -3580,7 +3580,7 @@ dhcp_flags=""</programlisting>
</itemizedlist> </itemizedlist>
<para>As one can see, the more specific part of a hostname appears to <para>As one can see, the more specific part of a hostname appears to
its left. For example, <hostid>foobardomain.org.</hostid> is more its left. For example, <hostid>foobar.org.</hostid> is more
specific than <hostid>org.</hostid>, as <hostid>org.</hostid> is specific than <hostid>org.</hostid>, as <hostid>org.</hostid> is
more specific than the root zone. The layout of each part of more specific than the root zone. The layout of each part of
a hostname is much like a filesystem: the <filename>/dev</filename> a hostname is much like a filesystem: the <filename>/dev</filename>
@ -3603,7 +3603,7 @@ dhcp_flags=""</programlisting>
world, replying authoritatively to queries.</para> world, replying authoritatively to queries.</para>
</listitem> </listitem>
<listitem> <listitem>
<para>a domain, such as <hostid>foobardomain.org</hostid>, is <para>a domain, such as <hostid>foobar.org</hostid>, is
registered and IP addresses need to be assigned to hostnames registered and IP addresses need to be assigned to hostnames
under it.</para> under it.</para>
</listitem> </listitem>
@ -3869,22 +3869,22 @@ zone "0.168.192.in-addr.arpa" {
<para>For each new zone served, a new zone entry must be added to <para>For each new zone served, a new zone entry must be added to
<filename>named.conf</filename></para> <filename>named.conf</filename></para>
<para>For example, the simplest zone entry for foobardomain.org can <para>For example, the simplest zone entry for foobar.org can
look like:</para> look like:</para>
<programlisting>zone "foobardomain.org" { <programlisting>zone "foobar.org" {
type master; type master;
file "foobardomain.org"; file "foobar.org";
};</programlisting> };</programlisting>
<para>The zone is a master, as indicated by the <option>type</option> <para>The zone is a master, as indicated by the <option>type</option>
statement, holding its zone information in statement, holding its zone information in
<filename>/etc/namedb/foobardomain.org</filename> indicated by <filename>/etc/namedb/foobar.org</filename> indicated by
the <option>file</option> statement.</para> the <option>file</option> statement.</para>
<programlisting>zone "foobardomain.org" { <programlisting>zone "foobar.org" {
type slave; type slave;
file "foobardomain.org"; file "foobar.org";
};</programlisting> };</programlisting>
<para>In the slave case, the zone information is transferred from <para>In the slave case, the zone information is transferred from
@ -3897,14 +3897,14 @@ zone "0.168.192.in-addr.arpa" {
<sect3> <sect3>
<title>Zone Files</title> <title>Zone Files</title>
<para> <para>
An example master zone file for <hostid>foobardomain.org</hostid> An example master zone file for <hostid>foobar.org</hostid>
(existing within <filename>/etc/namedb/foobardomain.org</filename>) (existing within <filename>/etc/namedb/foobar.org</filename>)
is as follows: is as follows:
</para> </para>
<programlisting>$TTL 3600 <programlisting>$TTL 3600
foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. ( foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
5 ; Serial 5 ; Serial
10800 ; Refresh 10800 ; Refresh
3600 ; Retry 3600 ; Retry
@ -3912,8 +3912,8 @@ foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. (
86400 ) ; Minimum TTL 86400 ) ; Minimum TTL
; DNS Servers ; DNS Servers
@ IN NS ns1.foobardomain.org. @ IN NS ns1.foobar.org.
@ IN NS ns2.foobardomain.org. @ IN NS ns2.foobar.org.
; Machine Names ; Machine Names
localhost IN A 127.0.0.1 localhost IN A 127.0.0.1
@ -3926,7 +3926,7 @@ mail IN A 3.2.1.10
www IN CNAME @ www IN CNAME @
; MX Record ; MX Record
@ IN MX 10 mail.foobardomain.org.</programlisting> @ IN MX 10 mail.foobar.org.</programlisting>
<para> <para>
Note that every hostname ending in a <quote>.</quote> is an Note that every hostname ending in a <quote>.</quote> is an
@ -3934,9 +3934,9 @@ www IN CNAME @
<quote>.</quote> is referenced to the origin. For example, <quote>.</quote> is referenced to the origin. For example,
<literal>www</literal> is translated into <literal>www + <literal>www</literal> is translated into <literal>www +
origin</literal>. In our fictitious zone file, our origin origin</literal>. In our fictitious zone file, our origin
is <hostid>foobardomain.org.</hostid>, so is <hostid>foobar.org.</hostid>, so
<literal>www</literal> would translate to <literal>www</literal> would translate to
<hostid>www.foobardomain.org.</hostid> <hostid>www.foobar.org.</hostid>
</para> </para>
<para> <para>
@ -3992,7 +3992,7 @@ www IN CNAME @
</variablelist> </variablelist>
<programlisting> <programlisting>
foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. ( foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
5 ; Serial 5 ; Serial
10800 ; Refresh after 3 hours 10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour 3600 ; Retry after 1 hour
@ -4003,26 +4003,26 @@ foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. (
<variablelist> <variablelist>
<varlistentry> <varlistentry>
<term><hostid>foobardomain.org.</hostid></term> <term><hostid>foobar.org.</hostid></term>
<listitem><para>the domain name, also the origin for this <listitem><para>the domain name, also the origin for this
zone file.</para></listitem> zone file.</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><hostid>ns1.foobardomain.org.</hostid></term> <term><hostid>ns1.foobar.org.</hostid></term>
<listitem><para>the primary/authoritative name server for this <listitem><para>the primary/authoritative name server for this
zone</para></listitem> zone</para></listitem>
</varlistentry> </varlistentry>
<varlistentry> <varlistentry>
<term><literal>admin.foobardomain.org.</literal></term> <term><literal>admin.foobar.org.</literal></term>
<listitem><para>the responsible person for this zone, <listitem><para>the responsible person for this zone,
email address with @ email address with @
replaced. (<email>admin@foobardomain.org</email> becomes replaced. (<email>admin@foobar.org</email> becomes
<literal>admin.foobardomain.org</literal>)</para> <literal>admin.foobar.org</literal>)</para>
</listitem> </listitem>
</varlistentry> </varlistentry>
@ -4043,13 +4043,13 @@ foobardomain.org. IN SOA ns1.foobardomain.org. admin.foobardomain.org. (
</variablelist> </variablelist>
<programlisting> <programlisting>
@ IN NS ns1.foobardomain.org.</programlisting> @ IN NS ns1.foobar.org.</programlisting>
<para> <para>
This is an <varname>NS</varname> entry. Every name server that is going to reply This is an <varname>NS</varname> entry. Every name server that is going to reply
authoritatively for the zone must have one of these entries. authoritatively for the zone must have one of these entries.
The <literal>@</literal> as seen here could have been The <literal>@</literal> as seen here could have been
<literal>foobardomain.org.</literal> <literal>foobar.org.</literal>
The <literal>@</literal> translates to the origin. The <literal>@</literal> translates to the origin.
</para> </para>
@ -4062,9 +4062,9 @@ mail IN A 3.2.1.10
<para> <para>
The A record indicates machine names. As seen above, The A record indicates machine names. As seen above,
<hostid>ns1.foobardomain.org</hostid> would resolve to <hostid>ns1.foobar.org</hostid> would resolve to
3.2.1.2. Again, the origin symbol, <literal>@</literal>, is 3.2.1.2. Again, the origin symbol, <literal>@</literal>, is
used here, thus meaning <hostid>foobardomain.org</hostid> used here, thus meaning <hostid>foobar.org</hostid>
would resolve to <hostid>3.2.1.30</hostid>. would resolve to <hostid>3.2.1.30</hostid>.
</para> </para>
@ -4075,25 +4075,25 @@ www IN CNAME @</programlisting>
The canonical name record is usually used for giving aliases The canonical name record is usually used for giving aliases
to a machine. In the example, <hostid>www</hostid> is to a machine. In the example, <hostid>www</hostid> is
aliased to the machine addressed to the origin, or aliased to the machine addressed to the origin, or
<hostid>foobardomain.org</hostid> (3.2.1.30). <hostid>foobar.org</hostid> (3.2.1.30).
<varname>CNAME</varname>s can be used to provide alias <varname>CNAME</varname>s can be used to provide alias
hostnames, or round robin one hostname among multiple hostnames, or round robin one hostname among multiple
machines. machines.
</para> </para>
<programlisting> <programlisting>
@ IN MX 10 mail.foobardomain.org.</programlisting> @ IN MX 10 mail.foobar.org.</programlisting>
<para> <para>
The <varname>MX</varname> record indicates which mail servers are responsible The <varname>MX</varname> record indicates which mail servers are responsible
for handling incoming mail for the zone. for handling incoming mail for the zone.
mail.foobardomain.org is the hostname of the mail server, mail.foobar.org is the hostname of the mail server,
and 10 being the priority of that mail server. and 10 being the priority of that mail server.
</para> </para>
<para> <para>
One can have several mail servers, with priorities of 3, 2, One can have several mail servers, with priorities of 3, 2,
1. A mail server attempting to deliver to foobardomain.org 1. A mail server attempting to deliver to foobar.org
would first try the highest priority MX, then the second would first try the highest priority MX, then the second
highest, etc, until the mail can be properly delivered. highest, etc, until the mail can be properly delivered.
</para> </para>
@ -4106,20 +4106,20 @@ www IN CNAME @</programlisting>
<programlisting>$TTL 3600 <programlisting>$TTL 3600
1.2.3.in-addr.arpa. IN SOA ns1.foobardomain.org. admin.foobardomain.org. ( 1.2.3.in-addr.arpa. IN SOA ns1.foobar.org. admin.foobar.org. (
5 ; Serial 5 ; Serial
10800 ; Refresh 10800 ; Refresh
3600 ; Retry 3600 ; Retry
604800 ; Expire 604800 ; Expire
3600 ) ; Minimum 3600 ) ; Minimum
@ IN NS ns1.foobardomain.org. @ IN NS ns1.foobar.org.
@ IN NS ns2.foobardomain.org. @ IN NS ns2.foobar.org.
2 IN PTR ns1.foobardomain.org. 2 IN PTR ns1.foobar.org.
3 IN PTR ns2.foobardomain.org. 3 IN PTR ns2.foobar.org.
10 IN PTR mail.foobardomain.org. 10 IN PTR mail.foobar.org.
30 IN PTR foobardomain.org.</programlisting> 30 IN PTR foobar.org.</programlisting>
<para> <para>
This file gives the proper IP address to hostname mappings of our above This file gives the proper IP address to hostname mappings of our above
fictitious domain. fictitious domain.
@ -4431,7 +4431,7 @@ www IN CNAME @</programlisting>
example:</para> example:</para>
<programlisting>server ntplocal.example.com prefer <programlisting>server ntplocal.example.com prefer
server timeserver.foobardomain.org server timeserver.foobar.org
server ntp2a.example.net server ntp2a.example.net
driftfile /var/db/ntp.drift</programlisting> driftfile /var/db/ntp.drift</programlisting>