Home | History | Annotate | only in /src/external/bsd/nsd/dist/contrib/bind2nsd
Up to higher level directory
NameDateSize
bind2nsd/25-Feb-2026
ChangeLog07-Jan-20172.5K
chk_version07-Jan-20171.5K
COPYING07-Jan-20171K
etc/25-Feb-2026
install.sh07-Jan-20171.2K
MANIFEST07-Jan-2017241
README07-Jan-20171.6K
scripts/25-Feb-2026
set_version07-Jan-20172.2K
setup.py07-Jan-20171.8K
TODO07-Jan-20172.1K

README

      1 bind2nsd -- translate from BIND named.conf to NSD nsd.conf
      2          -- then, sync up configuration files with a Secure64 server
      3 
      4 
      5 To install these tools on Linux systems:
      6 
      7    # ./install.sh
      8 
      9 Then, copy bind2nsd.conf to the directory you will run these commands
     10 from (e.g., /etc/named or /etc/bind9) and then edit the values properly.
     11 
     12 Passwords for logging into a Secure64 system can be stored in the
     13 bind2nsd.conf file (as clear text only) or can be stored encrypted
     14 by using the 'password_file' config item and the s64-mkpw utility.
     15 
     16 
     17 --
     18 Copyright (c) 2007, Secure64 Software Corporation.
     19 
     20 Permission is hereby granted, free of charge, to any person obtaining a copy
     21 of this software and associated documentation files (the "Software"), to deal
     22 in the Software without restriction, including without limitation the rights
     23 to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
     24 copies of the Software, and to permit persons to whom the Software is
     25 furnished to do so, subject to the following conditions:
     26 
     27 The above copyright notice and this permission notice shall be included in
     28 all copies or substantial portions of the Software.
     29 
     30 THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
     31 IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
     32 FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
     33 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
     34 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
     35 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
     36 THE SOFTWARE.
     37 
     38