- WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
-->
-<!-- $Id: Bv9ARM.7.html,v 1.5.2.4 2000/08/22 19:29:14 gson Exp $ -->
+<!-- $Id: Bv9ARM.7.html,v 1.5.2.5 2000/09/18 17:02:12 gson Exp $ -->
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML EXPERIMENTAL 970324//EN">
<HTML>
<P CLASS="2LevelContinued">
<A NAME="pgfId=997376">
</A>
-Access to the dynamic update facility should be strictly limited. In earlier versions of BIND the only way to do this was based on the IP address of the host requesting the update. BIND 9BIND 9 also supports authenticating updates cryptographically by means of transaction signatures (TSIG). The use of TSIG is strongly recommended.</P>
+Access to the dynamic update facility should be strictly limited. In earlier versions of BIND the only way to do this was based on the IP address of the host requesting the update. BIND 9 also supports authenticating updates cryptographically by means of transaction signatures (TSIG). The use of TSIG is strongly recommended.</P>
<P CLASS="2LevelContinued">
<A NAME="pgfId=1006806">
</A>
Copyright (C) 2000 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
-$Id: Bv9ARM.txt,v 1.3.2.6 2000/08/22 19:29:20 gson Exp $
+$Id: Bv9ARM.txt,v 1.3.2.7 2000/09/18 17:02:13 gson Exp $
BIND 9 Administrator Reference Manual
July 2000
Access to the dynamic update facility should be strictly limited. In earlier
versions of BIND the only way to do this was based on the IP address of the
-host requesting the update. BIND 9BIND 9 also supports authenticating
+host requesting the update. BIND 9 also supports authenticating
updates cryptographically by means of transaction signatures (TSIG). The use
of TSIG is strongly recommended.
projects / thirdparty / bind9.git / commitdiff
