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

Use 'example.com' or 'example.org' for example domain names.

Browse source 
Submitted by:	nik as per RFC 2606
This commit is contained in:
Murray Stokely 2001-10-17 04:34:04 +00:00
parent 8bbe2ce27b
commit bb4f2b8bb0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=10971
2 changed files with 49 additions and 49 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

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

@ -120,10 +120,10 @@ default outside-gw UGSc 37 418 ppp0
localhost localhost UH 0 181 lo0
test0 0:e0:b5:36:cf:4f UHLW 5 63288 ed0 77
10.20.30.255 link#1 UHLW 1 2421
foobar.com link#1 UC 0 0
example.com link#1 UC 0 0
host1 0:e0:a8:37:8:1e UHLW 3 4601 lo0
host2 0:e0:a8:37:8:1e UHLW 0 5 lo0 =>
host2.foobar.com link#1 UC 0 0
host2.example.com link#1 UC 0 0
224 link#1 UC 0 0</screen>
<indexterm><primary>default route</primary></indexterm>
@ -161,7 +161,7 @@ host2.foobar.com link#1 UC 0 0
<para>FreeBSD will also add subnet routes for the local subnet (<hostid
role="ipaddr">10.20.30.255</hostid> is the broadcast address for the
subnet <hostid role="ipaddr">10.20.30</hostid>, and <hostid
role="domainname">foobar.com</hostid> is the domain name associated
role="domainname">example.com</hostid> is the domain name associated
with that subnet). The designation <literal>link#1</literal> refers
to the first Ethernet card in the machine. You will notice no
additional interface is specified for those.</para>
@ -3564,11 +3564,11 @@ dhcp_flags=""</programlisting>
<para><hostid>org.</hostid> is a zone under the root zone</para>
</listitem>
<listitem>
<para><hostid>foobar.org</hostid> is a zone under the org. zone</para>
<para><hostid>example.org</hostid> is a zone under the org. zone</para>
</listitem>
<listitem>
<para><hostid>foo.foobar.org.</hostid> is a subdomain, a zone under the
<hostid>foobar.org.</hostid> zone
<para><hostid>foo.example.org.</hostid> is a subdomain, a zone under the
<hostid>example.org.</hostid> zone
</para>
</listitem>
<listitem>
@ -3580,7 +3580,7 @@ dhcp_flags=""</programlisting>
</itemizedlist>
<para>As one can see, the more specific part of a hostname appears to
its left. For example, <hostid>foobar.org.</hostid> is more
its left. For example, <hostid>example.org.</hostid> is more
specific than <hostid>org.</hostid>, as <hostid>org.</hostid> is
more specific than the root zone. The layout of each part of
a hostname is much like a filesystem: the <filename>/dev</filename>
@ -3603,7 +3603,7 @@ dhcp_flags=""</programlisting>
world, replying authoritatively to queries.</para>
</listitem>
<listitem>
<para>a domain, such as <hostid>foobar.org</hostid>, is
<para>a domain, such as <hostid>example.org</hostid>, is
registered and IP addresses need to be assigned to hostnames
under it.</para>
</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
<filename>named.conf</filename></para>
<para>For example, the simplest zone entry for foobar.org can
<para>For example, the simplest zone entry for example.org can
look like:</para>
<programlisting>zone "foobar.org" {
<programlisting>zone "example.org" {
type master;
file "foobar.org";
file "example.org";
};</programlisting>
<para>The zone is a master, as indicated by the <option>type</option>
statement, holding its zone information in
<filename>/etc/namedb/foobar.org</filename> indicated by
<filename>/etc/namedb/example.org</filename> indicated by
the <option>file</option> statement.</para>
<programlisting>zone "foobar.org" {
<programlisting>zone "example.org" {
type slave;
file "foobar.org";
file "example.org";
};</programlisting>
<para>In the slave case, the zone information is transferred from
@ -3897,14 +3897,14 @@ zone "0.168.192.in-addr.arpa" {
<sect3>
<title>Zone Files</title>
<para>
An example master zone file for <hostid>foobar.org</hostid>
(existing within <filename>/etc/namedb/foobar.org</filename>)
An example master zone file for <hostid>example.org</hostid>
(existing within <filename>/etc/namedb/example.org</filename>)
is as follows:
</para>
<programlisting>$TTL 3600
foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
example.org. IN SOA ns1.example.org. admin.example.org. (
5 ; Serial
10800 ; Refresh
3600 ; Retry
@ -3912,8 +3912,8 @@ foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
86400 ) ; Minimum TTL
; DNS Servers
@ IN NS ns1.foobar.org.
@ IN NS ns2.foobar.org.
@ IN NS ns1.example.org.
@ IN NS ns2.example.org.
; Machine Names
localhost IN A 127.0.0.1
@ -3926,7 +3926,7 @@ mail IN A 3.2.1.10
www IN CNAME @
; MX Record
@ IN MX 10 mail.foobar.org.</programlisting>
@ IN MX 10 mail.example.org.</programlisting>
<para>
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,
<literal>www</literal> is translated into <literal>www +
origin</literal>. In our fictitious zone file, our origin
is <hostid>foobar.org.</hostid>, so
is <hostid>example.org.</hostid>, so
<literal>www</literal> would translate to
<hostid>www.foobar.org.</hostid>
<hostid>www.example.org.</hostid>
</para>
<para>
@ -3992,7 +3992,7 @@ www IN CNAME @
</variablelist>
<programlisting>
foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
example.org. IN SOA ns1.example.org. admin.example.org. (
5 ; Serial
10800 ; Refresh after 3 hours
3600 ; Retry after 1 hour
@ -4003,26 +4003,26 @@ foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
<variablelist>
<varlistentry>
<term><hostid>foobar.org.</hostid></term>
<term><hostid>example.org.</hostid></term>
<listitem><para>the domain name, also the origin for this
zone file.</para></listitem>
</varlistentry>
<varlistentry>
<term><hostid>ns1.foobar.org.</hostid></term>
<term><hostid>ns1.example.org.</hostid></term>
<listitem><para>the primary/authoritative name server for this
zone</para></listitem>
</varlistentry>
<varlistentry>
<term><literal>admin.foobar.org.</literal></term>
<term><literal>admin.example.org.</literal></term>
<listitem><para>the responsible person for this zone,
email address with @
replaced. (<email>admin@foobar.org</email> becomes
<literal>admin.foobar.org</literal>)</para>
replaced. (<email>admin@example.org</email> becomes
<literal>admin.example.org</literal>)</para>
</listitem>
</varlistentry>
@ -4043,13 +4043,13 @@ foobar.org. IN SOA ns1.foobar.org. admin.foobar.org. (
</variablelist>
<programlisting>
@ IN NS ns1.foobar.org.</programlisting>
@ IN NS ns1.example.org.</programlisting>
<para>
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.
The <literal>@</literal> as seen here could have been
<literal>foobar.org.</literal>
<literal>example.org.</literal>
The <literal>@</literal> translates to the origin.
</para>
@ -4062,9 +4062,9 @@ mail IN A 3.2.1.10
<para>
The A record indicates machine names. As seen above,
<hostid>ns1.foobar.org</hostid> would resolve to
<hostid>ns1.example.org</hostid> would resolve to
3.2.1.2. Again, the origin symbol, <literal>@</literal>, is
used here, thus meaning <hostid>foobar.org</hostid>
used here, thus meaning <hostid>example.org</hostid>
would resolve to <hostid>3.2.1.30</hostid>.
</para>
@ -4075,25 +4075,25 @@ www IN CNAME @</programlisting>
The canonical name record is usually used for giving aliases
to a machine. In the example, <hostid>www</hostid> is
aliased to the machine addressed to the origin, or
<hostid>foobar.org</hostid> (3.2.1.30).
<hostid>example.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>
@ IN MX 10 mail.foobar.org.</programlisting>
@ IN MX 10 mail.example.org.</programlisting>
<para>
The <varname>MX</varname> record indicates which mail servers are responsible
for handling incoming mail for the zone.
mail.foobar.org is the hostname of the mail server,
mail.example.org is the hostname of the mail server,
and 10 being the priority of that mail server.
</para>
<para>
One can have several mail servers, with priorities of 3, 2,
1. A mail server attempting to deliver to foobar.org
1. A mail server attempting to deliver to example.org
would first try the highest priority MX, then the second
highest, etc, until the mail can be properly delivered.
</para>
@ -4106,20 +4106,20 @@ www IN CNAME @</programlisting>
<programlisting>$TTL 3600
1.2.3.in-addr.arpa. IN SOA ns1.foobar.org. admin.foobar.org. (
1.2.3.in-addr.arpa. IN SOA ns1.example.org. admin.example.org. (
5 ; Serial
10800 ; Refresh
3600 ; Retry
604800 ; Expire
3600 ) ; Minimum
@ IN NS ns1.foobar.org.
@ IN NS ns2.foobar.org.
@ IN NS ns1.example.org.
@ IN NS ns2.example.org.
2 IN PTR ns1.foobar.org.
3 IN PTR ns2.foobar.org.
10 IN PTR mail.foobar.org.
30 IN PTR foobar.org.</programlisting>
2 IN PTR ns1.example.org.
3 IN PTR ns2.example.org.
10 IN PTR mail.example.org.
30 IN PTR example.org.</programlisting>
<para>
This file gives the proper IP address to hostname mappings of our above
fictitious domain.
@ -4431,7 +4431,7 @@ www IN CNAME @</programlisting>
example:</para>
<programlisting>server ntplocal.example.com prefer
server timeserver.foobar.org
server timeserver.example.org
server ntp2a.example.net
driftfile /var/db/ntp.drift</programlisting>

10
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -3093,11 +3093,11 @@ spdadd 10.6.7.8 10.2.3.4 any -P out ipsec
&man.rlogin.1;.
</para>
<screen>&prompt.root <userinput>ssh <replaceable>user@foobardomain.com</replaceable></userinput>
<screen>&prompt.root <userinput>ssh <replaceable>user@example.com</replaceable></userinput>
Host key not found from the list of known hosts.
Are you sure you want to continue connecting (yes/no)? <userinput>yes</userinput>
Host 'foobardomain.com' added to the list of known hosts.
user@foobardomain.com's password: <userinput>*******</userinput></screen>
Host 'example.com' added to the list of known hosts.
user@example.com's password: <userinput>*******</userinput></screen>
<para>The login will continue just as it would have if a session was
created using <command>rlogin</command> or telnet. SSH utilizes a
@ -3134,8 +3134,8 @@ user@foobardomain.com's password: <userinput>*******</userinput></screen>
it copies a file to or from a remote machine, except in a
secure fashion.</para>
<screen>&prompt.root <userinput> scp <replaceable>user@foobardomain.com:/COPYRIGHT COPYRIGHT</replaceable></userinput>
user@foobardomain.com's password:
<screen>&prompt.root <userinput> scp <replaceable>user@example.com:/COPYRIGHT COPYRIGHT</replaceable></userinput>
user@example.com's password:
COPYRIGHT 100% |*****************************| 4735
00:00
&prompt.root</screen>