| /netbsd-src/external/mpl/bind/dist/doc/arm/ |
| H A D | history.rst | 14 A Brief History of the DNS and BIND 34 Domain (BIND) package, was written soon after by a group of graduate 38 Versions of BIND through 4.8.3 were maintained by the Computer Systems 40 Riggle, and Songnian Zhou made up the initial BIND project team. After 43 to the CSRG, worked on BIND for 2 years, from 1985 to 1987. Many other 44 people also contributed to BIND development during that time: Doug 46 and Mike Schwartz. BIND maintenance was subsequently handled by Mike 49 BIND versions 4.9 and 4.9.1 were released by Digital Equipment 52 employee, became BIND's primary caretaker. He was assisted by Phil 58 In 1994, BIND version 4.9.2 was sponsored by Vixie Enterprises. Paul [all …]
|
| H A D | introduction.inc.rst | 14 Introduction to DNS and BIND 9 30 The Berkeley Internet Name Domain (BIND) software implements a domain name server 33 Consortium (ISC) BIND version 9 software package for system 36 This manual covers BIND version |release|. 43 :ref:`introduction` introduces the basic DNS and BIND concepts. Some tutorial material on 45 :ref:`intro_dns_security` is provided to allow BIND operators to implement 48 :ref:`requirements` describes the hardware and environment requirements for BIND 9 56 :ref:`ns_operations` covers basic BIND 9 software and DNS operations, including some 62 :ref:`security` covers most aspects of BIND 9 security, including file permissions, 63 running BIND 9 in a "jail," and securing file transfers and dynamic updates. [all …]
|
| H A D | platforms.inc.rst | 17 The current support status of BIND 9 versions across various platforms can be 22 In general, this version of BIND will build and run on any 27 The following C11 features are required to compile BIND 9: 33 Where it makes sense, BIND 9 uses C-standard fixes introduced by the C17 update 36 ISC regularly tests BIND on many operating systems and architectures, 43 Current versions of BIND 9 are fully supported and regularly tested on the 58 The following are platforms on which BIND is known to build and run. ISC 81 BIND easily available, although it is possible in many cases to 100 These are platforms on which current versions of BIND 9 are known *not* to build or run: 111 Installing BIND [all...] |
| H A D | notes.rst | 22 BIND 9.20 is a stable branch, suitable for production use. This 35 The latest versions of BIND 9 software can always be found at 46 https://gitlab.isc.org/isc-projects/bind9/-/wikis/Known-Issues-in-BIND-9.20 59 BIND 9 is open source software licensed under the terms of the Mozilla Public 68 BIND 9.20 is a stable branch, suitable for production use. After it has 70 Support Version (ESV). Until then, the current ESV is BIND 9.18, which
|
| H A D | security.inc.rst | 19 BIND 9's design assumes that access to the objects listed below is limited only to 36 such a situation, BIND implements its own safety checks and limits which are 55 for this amplification, but BIND implements its own limits to balance 65 BIND*. 131 When BIND 9 is built with GeoIP support, ACLs can also be used for 206 On Unix servers, it is possible to run BIND in a *chrooted* environment 208 :iscman:`named`. This can help improve system security by placing BIND in a 211 Another useful feature in the Unix version of BIND is the ability to run 215 Here is an example command line to load BIND in a ``chroot`` sandbox, 227 environment must include everything BIND need [all...] |
| H A D | dyndb.inc.rst | 17 Dynamic Database, or DynDB, is an extension to BIND 9 which, like DLZ (see 19 database. Unlike DLZ, a DynDB module provides a full-featured BIND zone 25 natively by BIND. 31 with the BIND source code, in the directory 54 treated as normal authoritative zones when BIND responds to
|
| H A D | intro-security.inc.rst | 20 appropriate solutions. BIND 9, a specific implementation of the DNS protocol, 36 BIND 9 Security Overview 41 BIND 9's local environment, including :ref:`file permissions <file_permissions>`, running 42 BIND 9 in a :ref:`jail <chroot_and_setuid>`, and the use of :ref:`Access_Control_Lists`. 45 administrator to control the operation of a name server. The majority of BIND 9 packages 73 DNS tools that implement DNSSEC. BIND 9 may be configured to provide such capability on supported Linux or Unix platforms.
|
| H A D | troubleshooting.inc.rst | 37 drop EDNS queries rather than replying with FORMERR. BIND and other 46 was implemented in BIND as of release 9.14.0. 77 BIND 9 is built against. For OpenSSL, version 1.1.1 or newer is 117 Due to the limitations of the current logging code in BIND 9, 149 The BIND-users mailing list, at https://lists.isc.org/mailman/listinfo/bind-users, is an excellent … 154 for BIND 9, ISC DHCP, and Kea DHCP.
|
| /netbsd-src/external/bsd/nsd/dist/doc/ |
| H A D | differences.tex | 32 BIND 8.4.7 and BIND 9.3.2. Differences in answers to captured queries from 47 We used BIND 8 and BIND 9 versions to compare against. Also regression 58 both BIND and NSD are mature and stable DNS implementations, all answers 80 BIND 9.3.2 remained running and responsive. 85 These traces posed no problem for BIND and NSD, mostly FORMERR answers. 87 A previous document DIFFERENCES between BIND 8.4.4 and NSD 2.0.0 can be found 90 In the places where differences have been found between BIND and NSD, 94 \section{Response differences between BIND 9.3.2 and NSD 3.0.0} 96 In this section the response differences between BIND 9.3.2 and NSD 3.0.0 107 Comparison between NSD 3.0.0 and BIND 9.3.2 for a root trace. [all …]
|
| H A D | NSD-FOR-BIND-USERS | 1 NSD for BIND users 16 assumes the reader is familiar with BIND tools and explains 17 the differences between BIND and NSD. 43 The config file for NSD nsd.conf(5) is different from BIND named.conf(5). 47 A short configuration file for BIND can look like this: 117 BIND associates TSIG keys with an IP address. When communicating from/to 118 that address BIND will TSIG sign. NSD associates TSIG keys with the 125 In BIND you might have a master that uses tsig for zone updates. 135 // when BIND communicates with this server, use the key 161 # the allow-transfer and server statements from BIND rolled into one. [all …]
|
| /netbsd-src/external/mpl/bind/ |
| H A D | binclude4netbsd | 23 BIND=$1 27 cp $BIND/config.h $INCLUDE 31 cp $BIND/lib/dns/code.h $INCLUDE/dns 35 cp $BIND/lib/dns/include/dns/$i $INCLUDE/dns 40 cp $BIND/lib/isc/include/isc/platform.h $INCLUDE/isc 48 cp $BIND/lib/$d/include/$d/$i $INCLUDE/$d
|
| /netbsd-src/external/mpl/dhcp/ |
| H A D | Makefile.inc | 13 BIND:= ${.PARSEDIR}/bind 14 BINDDIST= ${BIND}/dist 38 PROGDPLIBS+= irs ${BIND}/lib/libirs 39 PROGDPLIBS+= isccfg ${BIND}/lib/libisccfg 40 PROGDPLIBS+= dns ${BIND}/lib/libdns 41 PROGDPLIBS+= isc ${BIND}/lib/libisc
|
| /netbsd-src/external/mpl/bind/dist/doc/notes/ |
| H A D | notes-9.18.0.rst | |
| H A D | notes-9.18.8.rst | |
| H A D | notes-9.18.7.rst | |
| H A D | notes-9.18.9.rst | |
| H A D | notes-9.18.15.rst | |
| H A D | notes-9.18.17.rst | |
| H A D | notes-9.18.16.rst | |
| H A D | notes-9.18.1.rst | |
| H A D | notes-9.18.18.rst | |
| H A D | notes-9.18.10.rst | |
| /netbsd-src/external/bsd/libbind/dist/ |
| H A D | README | 16 Originally written for BIND 8, it was included in BIND 9 as 18 removed from subsequent releases of BIND 9 and is now 93 - Installing both libbind and BIND 9 on the same system 95 names: $PREFIX/include/isc/list.h (from BIND 9) and 111 Discussions of libbind can be send to the BIND Users mailing 121 code, you might want to join the BIND Workers mailing list.
|
| /netbsd-src/external/mpl/dhcp/dist/doc/ |
| H A D | BIND-libraries | 1 Current ISC DHCP uses the BIND 9 libraries for some services. 11 BIND 9 must be built and installed before ISC DHCP build is configured. 34 external BIND 9 libraries 49 not used for embedded libraries but used by BIND 9 54 not used for embedded nor BIND 9 for its includes and libraries 67 ignored by embedded or BIND 9 libraries configure 70 parallel builds don't work for embedded or BIND 9 libraries build 126 please leave embedded or BIND 9 libraries configure to do its job
|
| /netbsd-src/external/bsd/nsd/dist/contrib/ |
| H A D | README | 20 DNS information in BIND format to NSD format, and then copy that 22 redundant BIND and NSD servers and keep them in sync, using only the 23 BIND configuration files
|