- Make the section about using applications with IPv6 a little more generic and move it to the end where it fits better.
- Add Hurricane Electric as a Tunnel Broker. Reviewed by: gavin@, Ken Reed <kreed002@gmail.com>
This commit is contained in:
parent
9876932e7c
commit
f5c2c80757
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=42596
1 changed files with 23 additions and 20 deletions
|
@ -5288,6 +5288,12 @@ redirect_port tcp 192.168.0.3:80 80</programlisting>
|
|||
<para><ulink url="http://www.sixxs.net">SixXS</ulink> offers
|
||||
tunnels with end-points all around the globe.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink url="http://www.tunnelbroker.net">Hurricane
|
||||
Electric</ulink> offers tunnels with end-points all around
|
||||
the globe.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Tunnel via 6-to-4 as described in <ulink
|
||||
|
@ -5302,26 +5308,6 @@ redirect_port tcp 192.168.0.3:80 80</programlisting>
|
|||
</itemizedlist>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title><acronym>DNS</acronym> in the <acronym>IPv6</acronym>
|
||||
World</title>
|
||||
|
||||
<para>There used to be two types of <acronym>DNS</acronym>
|
||||
records for <acronym>IPv6</acronym>. The
|
||||
<acronym>IETF</acronym> has declared <acronym>AAAA</acronym>
|
||||
records as the current standard.</para>
|
||||
|
||||
<para>Using <acronym>AAAA</acronym> records is straightforward.
|
||||
Assign the hostname to the <acronym>IPv6</acronym> address
|
||||
in the primary zone <acronym>DNS</acronym> file:</para>
|
||||
|
||||
<programlisting>MYHOSTNAME AAAA MYIPv6ADDR</programlisting>
|
||||
|
||||
<para>Current versions of &man.named.8; and <filename
|
||||
role="package">dns/djbdns</filename> support
|
||||
<acronym>AAAA</acronym> records.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Applying the Needed Changes to
|
||||
<filename>/etc/rc.conf</filename></title>
|
||||
|
@ -5495,6 +5481,23 @@ redirect_port tcp 192.168.0.3:80 80</programlisting>
|
|||
section 3.6 and 3.7 as well as <acronym>RFC</acronym> 4038
|
||||
section 4.2 may be useful to some adminstrators.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Application Use of <acronym>IPv6</acronym></title>
|
||||
|
||||
<para>Currently <acronym>IPv6</acronym> support for many
|
||||
applications and services is very good, though for some
|
||||
software it still needs work. For authoritative
|
||||
information about the support of
|
||||
<acronym>IPv6</acronym>, please consult the Official
|
||||
Documentation for the software in question.</para>
|
||||
|
||||
<para>Web, <acronym>DNS</acronym> and Mail applications
|
||||
and servers have the best support for
|
||||
<acronym>IPv6</acronym> because they are the most common
|
||||
use case. Other applications may have varying degrees
|
||||
of <acronym>IPv6</acronym> support.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="network-atm">
|
||||
|
|
Loading…
Reference in a new issue