Use example.com or example.org for domain names in examples instead of
variations of "foobar" and the like. Submitted by: nik and dougb (per RFC 2606)
This commit is contained in:
Murray Stokely
parent
bb4f2b8bb0
commit
597ccea2b5
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10972
9 changed files with 48 additions and 48 deletions
|
|
@ -38,10 +38,10 @@
|
|||
terminal required first creating a diskless system with minimal
|
||||
utilities mounted via NFS. These same steps were used to create 2
|
||||
separate diskless systems. The first is <hostid
|
||||
role="fqdn">altair.kcis.com</hostid>. A diskless X terminal that I
|
||||
role="fqdn">altair.example.com</hostid>. A diskless X terminal that I
|
||||
run on my old 386DX-40. It has a 340Meg hard disk but, I did not want
|
||||
to change it. So, it boots from <hostid
|
||||
role="fqdn">antares.kcis.com</hostid> across a Ethernet. The second
|
||||
role="fqdn">antares.example.com</hostid> across a Ethernet. The second
|
||||
system is a 486DX2-66. I setup a diskless FreeBSD (complete) that
|
||||
uses no local disk. The server in that case is a Sun 670MP running
|
||||
SunOS 4.1.3. The same setup configuration was needed for both.</para>
|
||||
|
|
@ -256,9 +256,9 @@ bootps dgram udp wait root /usr/libexec/bootpd bootpd /etc/bootptab</progra
|
|||
<filename>/tftpboot/cfg.199.246.76.2</filename>. The contents is:</para>
|
||||
|
||||
<programlisting>rootfs 199.246.76.1:/DiskLess/rootfs/altair
|
||||
hostname altair.kcis.com</programlisting>
|
||||
hostname altair.example.com</programlisting>
|
||||
|
||||
<para>The line <literal>hostname altair.kcis.com</literal> simply tells
|
||||
<para>The line <literal>hostname altair.example.com</literal> simply tells
|
||||
the diskless system what its fully qualified domain name is.</para>
|
||||
|
||||
<para>The line <literal>rootfs
|
||||
|
|
|
|||
|
|
@ -19,7 +19,7 @@
|
|||
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.271 2001/10/03 20:29:11 ue Exp $</pubdate>
|
||||
<pubdate>$FreeBSD$</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1995</year>
|
||||
|
|
@ -8633,11 +8633,11 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
|
|||
|
||||
<answer>
|
||||
<para>You will probably find that the host is actually in a
|
||||
different domain; for example, if you are in foo.bar.edu and
|
||||
different domain; for example, if you are in foo.example.org and
|
||||
you wish to reach a host called <hostid>mumble</hostid> in the
|
||||
<hostid role="domainname">bar.edu</hostid> domain, you will
|
||||
<hostid role="domainname">example.org</hostid> domain, you will
|
||||
have to refer to it by the fully-qualified domain name, <hostid
|
||||
role="fqdn">mumble.bar.edu</hostid>, instead of just
|
||||
role="fqdn">mumble.example.org</hostid>, instead of just
|
||||
<hostid>mumble</hostid>.</para>
|
||||
|
||||
<para>Traditionally, this was allowed by BSD BIND resolvers.
|
||||
|
|
@ -8647,23 +8647,23 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
|
|||
abbreviations for non-fully qualified domain names other than
|
||||
the domain you are in. So an unqualified host
|
||||
<hostid>mumble</hostid> must either be found as <hostid
|
||||
role="fqdn">mumble.foo.bar.edu</hostid>, or it will be searched
|
||||
role="fqdn">mumble.foo.example.org</hostid>, or it will be searched
|
||||
for in the root domain.</para>
|
||||
|
||||
<para>This is different from the previous behavior, where the
|
||||
search continued across
|
||||
<hostid role="domainname">mumble.bar.edu</hostid>, and
|
||||
<hostid role="domainname">mumble.example.org</hostid>, and
|
||||
<hostid role="domainname">mumble.edu</hostid>. Have a look at
|
||||
RFC 1535 for why this was considered bad practice, or even a
|
||||
security hole.</para>
|
||||
|
||||
<para>As a good workaround, you can place the line</para>
|
||||
|
||||
<programlisting>search foo.bar.edu bar.edu</programlisting>
|
||||
<programlisting>search foo.example.org example.org</programlisting>
|
||||
|
||||
<para>instead of the previous</para>
|
||||
|
||||
<programlisting>domain foo.bar.edu</programlisting>
|
||||
<programlisting>domain foo.example.org</programlisting>
|
||||
|
||||
<para>into your
|
||||
<filename>/etc/resolv.conf</filename> file (see &man.resolv.conf.5;). However, make sure that the
|
||||
|
|
@ -8825,9 +8825,9 @@ round-trip min/avg/max/stddev = 2.530/2.643/2.774/0.103 ms</screen>
|
|||
tree in category <quote>sysutils</quote>. Simply replace the
|
||||
service's commandline to call socket instead, like so:</para>
|
||||
|
||||
<programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket <replaceable>ftp.foo.com</replaceable> <replaceable>ftp</replaceable></programlisting>
|
||||
<programlisting>ftp stream tcp nowait nobody /usr/local/bin/socket socket <replaceable>ftp.example.com</replaceable> <replaceable>ftp</replaceable></programlisting>
|
||||
|
||||
<para>where <replaceable>ftp.foo.com</replaceable> and
|
||||
<para>where <replaceable>ftp.example.com</replaceable> and
|
||||
<replaceable>ftp</replaceable> are the host and port to
|
||||
redirect to, respectively.</para>
|
||||
</answer>
|
||||
|
|
|
|||
|
|
@ -1244,7 +1244,7 @@ Exports list on foobar:
|
|||
max-lease-time 7200;
|
||||
authoritative;
|
||||
|
||||
option domain-name "mydom.com";
|
||||
option domain-name "example.com";
|
||||
option domain-name-servers 192.168.4.1;
|
||||
option routers 192.168.4.1;
|
||||
|
||||
|
|
@ -1255,7 +1255,7 @@ Exports list on foobar:
|
|||
|
||||
host margaux {
|
||||
hardware ethernet 01:23:45:67:89:ab;
|
||||
fixed-address margaux.mydom.com;
|
||||
fixed-address margaux.example.com;
|
||||
next-server 192.168.4.4;<co id="co-dhcp-next-server">
|
||||
filename "/tftpboot/kernel.diskless";<co id="co-dhcp-filename">
|
||||
option root-path "192.168.4.4:/data/misc/diskless";<co id="co-dhcp-root-path">
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.25 2001/09/04 08:27:33 murray Exp $
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<chapter id="config-tuning">
|
||||
|
|
@ -271,7 +271,7 @@
|
|||
<itemizedlist>
|
||||
<listitem><para>rc.conf:</para>
|
||||
<programlisting> . rc.conf.site
|
||||
hostname="node15.webcompany.com"
|
||||
hostname="node15.example.com"
|
||||
network_interfaces="fxp0 lo0"
|
||||
ifconfig_fxp0="inet 10.1.1.1"</programlisting></listitem>
|
||||
<listitem><para>rc.conf.site:</para>
|
||||
|
|
@ -574,7 +574,7 @@ exit 0
|
|||
|
||||
<para>A typical <filename>resolv.conf</filename>:</para>
|
||||
|
||||
<programlisting>search foobar.com
|
||||
<programlisting>search example.com
|
||||
nameserver 147.11.1.11
|
||||
nameserver 147.11.100.30</programlisting>
|
||||
|
||||
|
|
@ -635,7 +635,7 @@ nameserver 147.11.100.30</programlisting>
|
|||
|
||||
<para>For example:</para>
|
||||
|
||||
<programlisting>10.0.0.1 myRealHostname.foobar.com myRealHostname foobar1 foobar2</programlisting>
|
||||
<programlisting>10.0.0.1 myRealHostname.example.com myRealHostname foobar1 foobar2</programlisting>
|
||||
|
||||
<para>Consult &man.hosts.5; for more information.</para>
|
||||
</sect3>
|
||||
|
|
|
|||
|
|
@ -528,7 +528,7 @@ subscribe freebsd-announce
|
|||
highly appreciated by us!), you would do something like:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>mail majordomo@FreeBSD.org</userinput>
|
||||
subscribe freebsd-announce local-announce@somesite.com
|
||||
subscribe freebsd-announce local-announce@example.com
|
||||
^D</screen>
|
||||
|
||||
<para>Finally, it is also possible to unsubscribe yourself from a list,
|
||||
|
|
|
|||
|
|
@ -2684,18 +2684,18 @@ Mounting root from ufs:/dev/md0c
|
|||
<quote>@</quote> sign. The proxy server then <quote>fakes</quote>
|
||||
the real server. For example, assuming you want to install from
|
||||
<hostid role="fqdn">ftp.FreeBSD.org</hostid>, using the proxy FTP
|
||||
server <hostid role="fqdn">foo.bar.com</hostid>, listening on port
|
||||
server <hostid role="fqdn">foo.example.com</hostid>, listening on port
|
||||
1024.</para>
|
||||
|
||||
<para>In this case, you go to the options menu, set the FTP username
|
||||
to <literal>ftp@ftp.FreeBSD.org</literal>, and the password to your
|
||||
email address. As your installation media, you specify FTP (or
|
||||
passive FTP, if the proxy supports it), and the URL
|
||||
<literal>ftp://foo.bar.com:1234/pub/FreeBSD</literal>.</para>
|
||||
<literal>ftp://foo.example.com:1234/pub/FreeBSD</literal>.</para>
|
||||
|
||||
<para>Since <filename>/pub/FreeBSD</filename> from
|
||||
<hostid role="fqdn">ftp.FreeBSD.org</hostid> is proxied under
|
||||
<hostid role="fqdn">foo.bar.com</hostid>, you are able to install
|
||||
<hostid role="fqdn">foo.example.com</hostid>, you are able to install
|
||||
from <emphasis>that</emphasis> machine (which will fetch the files
|
||||
from <hostid role="fqdn">ftp.FreeBSD.org</hostid> as your
|
||||
installation requests them.</para>
|
||||
|
|
@ -2859,7 +2859,7 @@ installation menus to try and retry whichever operations have failed.
|
|||
<term>Host</term>
|
||||
|
||||
<listitem>
|
||||
<para>The fully-qualified hostname, e.g. k6-2.weeble.com in
|
||||
<para>The fully-qualified hostname, e.g. k6-2.example.com in
|
||||
this case.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
@ -2869,7 +2869,7 @@ installation menus to try and retry whichever operations have failed.
|
|||
|
||||
<listitem>
|
||||
<para>The name of the domain that your machine is
|
||||
in, e.g. weeble.com for this case.</para>
|
||||
in, e.g. example.com for this case.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
||||
|
|
@ -4319,13 +4319,13 @@ Generating RSA keys: Key generation complete.
|
|||
Your identification has been saved in /etc/ssh/ssh_host_key.
|
||||
Your public key has been saved in /etc/ssh/ssh_host_key.pub.
|
||||
The key fingerprint is:
|
||||
2d:02:37:d2:0e:68:93:8f:9c:46:de:92:f4:be:60:0a root@k6-2.weeble.com
|
||||
2d:02:37:d2:0e:68:93:8f:9c:46:de:92:f4:be:60:0a root@k6-2.example.com
|
||||
creating ssh DSA host key
|
||||
Generating DSA parameter and key.
|
||||
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
|
||||
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
|
||||
The key fingerprint is:
|
||||
38:af:d2:1f:63:14:00:d8:83:fd:dd:4b:97:1c:43:6d root@k6-2.weeble.com.
|
||||
38:af:d2:1f:63:14:00:d8:83:fd:dd:4b:97:1c:43:6d root@k6-2.example.com.
|
||||
setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib
|
||||
/usr/local/lib
|
||||
setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
|
||||
|
|
@ -4337,7 +4337,7 @@ Additional ABI support: linux.
|
|||
Local package initilization:.
|
||||
Additional TCP options:.
|
||||
|
||||
FreeBSD/i386 (k6-2.weeble.com) (ttyv0)
|
||||
FreeBSD/i386 (k6-2.example.com) (ttyv0)
|
||||
|
||||
login: rpratt
|
||||
Password:</screen>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.38 2001/09/05 21:32:46 chern Exp $
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<chapter id="mail">
|
||||
|
|
@ -338,7 +338,7 @@ okay.cyberspammer.com OK
|
|||
<hostid>another.source.of.spam</hostid>. The next entry accepts
|
||||
mail connections from a host
|
||||
<hostid>okay.cyberspammer.com</hostid>, which is more exact than
|
||||
the <hostid>cyberspamer.com</hostid> line above. More specific
|
||||
the <hostid>cyberspammer.com</hostid> line above. More specific
|
||||
matches override less exact matches. The last entry allows
|
||||
relaying of electronic mail from hosts with an IP address that
|
||||
begins with <hostid>128.32</hostid>. These hosts would be able
|
||||
|
|
|
|||
|
|
@ -350,13 +350,13 @@ bind</programlisting>
|
|||
contain
|
||||
entries for the machine which will be running ppp. Assuming
|
||||
that your machine is called <hostid
|
||||
role="fqdn">foo.bar.com</hostid> with the IP address <hostid
|
||||
role="fqdn">foo.example.com</hostid> with the IP address <hostid
|
||||
role="ipaddr">10.0.0.1</hostid>,
|
||||
<filename>/etc/hosts</filename> should contain:</para>
|
||||
|
||||
<programlisting>127.0.0.1 localhost.bar.com localhost
|
||||
::1 localhost.bar.com localhost
|
||||
10.0.0.1 foo.bar.com foo</programlisting>
|
||||
<programlisting>127.0.0.1 localhost.example.com localhost
|
||||
::1 localhost.example.com localhost
|
||||
10.0.0.1 foo.example.com foo</programlisting>
|
||||
|
||||
<para>The first two lines define the alias
|
||||
<hostid>localhost</hostid> as a synonym for the current
|
||||
|
|
@ -364,7 +364,7 @@ bind</programlisting>
|
|||
for these lines should always be <hostid
|
||||
role="ipaddr">127.0.0.1</hostid> and <hostid
|
||||
role="ipaddr">::1</hostid>. The last line maps
|
||||
the name <hostid role="fqdn">foo.bar.com</hostid> (and the
|
||||
the name <hostid role="fqdn">foo.example.com</hostid> (and the
|
||||
shorthand <hostid>foo</hostid>) to the IP address <hostid
|
||||
role="ipaddr">10.0.0.1</hostid>.</para>
|
||||
|
||||
|
|
@ -386,7 +386,7 @@ bind</programlisting>
|
|||
resolver how to behave. Normally, you will need to enter
|
||||
the following line(s):</para>
|
||||
|
||||
<programlisting>domain <replaceable>bar.com</replaceable>
|
||||
<programlisting>domain <replaceable>example.com</replaceable>
|
||||
nameserver <replaceable>x.x.x.x</replaceable>
|
||||
nameserver <replaceable>y.y.y.y</replaceable></programlisting>
|
||||
|
||||
|
|
@ -1199,7 +1199,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
<para>Working from the top down in this file, make sure the
|
||||
<literal>hostname=</literal> line is set, e.g.:</para>
|
||||
|
||||
<programlisting>hostname="foo.bar.com"</programlisting>
|
||||
<programlisting>hostname="foo.example.com"</programlisting>
|
||||
|
||||
<para>If your ISP has supplied you with a static IP address and
|
||||
name, it is probably best that you use this name as your host
|
||||
|
|
|
|||
|
|
@ -3238,7 +3238,7 @@ Your identification has been saved in /home/user/.ssh/identity.
|
|||
<para>The following command tells &man.ssh.1; to create a tunnel
|
||||
for telnet.</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5023:localhost:23 user@foo.bar.com</replaceable></userinput>
|
||||
<screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5023:localhost:23 user@foo.example.com</replaceable></userinput>
|
||||
&prompt.user;</screen>
|
||||
|
||||
<para>The <command>ssh</command> command is used with the
|
||||
|
|
@ -3285,7 +3285,7 @@ Your identification has been saved in /home/user/.ssh/identity.
|
|||
</varlistentry>
|
||||
|
||||
<varlistentry>
|
||||
<term><option>user@foo.bar.com</option></term>
|
||||
<term><option>user@foo.example.com</option></term>
|
||||
|
||||
<listitem>
|
||||
<para>The remote SSH server.</para>
|
||||
|
|
@ -3311,13 +3311,13 @@ Your identification has been saved in /home/user/.ssh/identity.
|
|||
</para>
|
||||
|
||||
<para>A typical SSH Tunnel</para>
|
||||
<screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5025:localhost:25 user@mailserver.foobar.com</replaceable></userinput>
|
||||
user@mailserver.foobar.com's password: <userinput>*****</userinput>
|
||||
<screen>&prompt.user; <userinput>ssh -2 -N -f -L <replaceable>5025:localhost:25 user@mailserver.example.com</replaceable></userinput>
|
||||
user@mailserver.example.com's password: <userinput>*****</userinput>
|
||||
&prompt.user; <userinput>telnet localhost 5025</userinput>
|
||||
Trying 127.0.0.1...
|
||||
Connected to localhost.
|
||||
Escape character is '^]'.
|
||||
220 mailserver.foobar.com ESMTP</screen>
|
||||
220 mailserver.example.com ESMTP</screen>
|
||||
|
||||
<para>This can be used in conjunction with an &man.ssh-keygen.1;
|
||||
and additional user accounts to create a more seamless/hassle-free
|
||||
|
|
@ -3340,13 +3340,13 @@ Escape character is '^]'.
|
|||
an SSH connection to your office's SSH server, and tunnel
|
||||
through to the mail server.</para>
|
||||
|
||||
<screen>&prompt.user; ssh -2 -N -f -L 2110:mail.office-foobar.com user@ssh-server.office-foobar.com
|
||||
user@ssh-server.office-foobar.com's password: ******</screen>
|
||||
<screen>&prompt.user; ssh -2 -N -f -L 2110:mail.example.com user@ssh-server.example.com
|
||||
user@ssh-server.example.com's password: ******</screen>
|
||||
|
||||
<para>When the tunnel is up and running, you can point your
|
||||
mail client to send POP3 requests to <hostid>localhost</hostid>
|
||||
port 2110. A connection here will be forwarded securely across
|
||||
the tunnel to <hostid>mail.office-foobar.com</hostid>.</para>
|
||||
the tunnel to <hostid>mail.example.com</hostid>.</para>
|
||||
</sect4>
|
||||
|
||||
<sect4>
|
||||
|
|
@ -3367,12 +3367,12 @@ user@ssh-server.office-foobar.com's password: ******</screen>
|
|||
outside of your network's firewall, and use it to tunnel to
|
||||
the Ogg Vorbis server.</para>
|
||||
|
||||
<screen>&prompt.user; ssh -2 -N -f -L 8888:music.foobar.com:8000 user@unfirewalled.myserver.com
|
||||
<screen>&prompt.user; ssh -2 -N -f -L 8888:music.example.com:8000 user@unfirewalled.myserver.com
|
||||
user@unfirewalled.myserver.com's password: *******</screen>
|
||||
|
||||
<para>Your streaming client can now be pointed to
|
||||
<hostid>localhost</hostid> port 8888, which will be
|
||||
forwarded over to <hostid>music.foobar.com</hostid> port
|
||||
forwarded over to <hostid>music.example.com</hostid> port
|
||||
8000, successfully evading the firewall.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
|
|
|||
Loading…
Reference in a new issue