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

Update Question 12.17:

Browse source 
- Replace the answer with a reference to the FreeBSD Handbook

Reviewed by:  trhodes, danger
Approved by:  gabor
This commit is contained in:
Gabor Pali 2008-06-21 08:19:12 +00:00
parent a0d35b35a8
commit 4e6508f994
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=32367
1 changed files with 3 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

42
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -7716,45 +7716,9 @@ Key F15 A A Menu Workplace Nop</programlisting>
</question>
<answer>
<para>You will probably find that the host is actually in a
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">example.org</hostid> domain, you will
have to refer to it by the fully-qualified domain name, <hostid
role="fqdn">mumble.example.org</hostid>, instead of just
<hostid>mumble</hostid>.</para>
<para>Traditionally, this was allowed by BSD BIND resolvers.
However the current version of
<application>bind</application> (see &man.named.8;)
that ships with FreeBSD no longer provides default
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.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.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.example.org example.org</programlisting>
<para>instead of the previous</para>
<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
search order does not go beyond the <quote>boundary
between local and public administration</quote>, as RFC
1535 calls it.</para>
</answer>
<para>See the answer in the &os; <ulink
url="&url.books.handbook;/mail-trouble.html">Handbook</ulink>.</para>
</answer>
</qandaentry>
<qandaentry>