diff --git a/CONTRIBUTING b/CONTRIBUTING index 003a7c85931e033c7d22181a0b7e1ff2d8ed07ad..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 100644 --- a/CONTRIBUTING +++ b/CONTRIBUTING @@ -1,186 +0,0 @@ -BIND Source Access and Contributor Guidelines - -Feb 22, 2018 - -Contents - - 1. Access to source code - 2. Reporting bugs - 3. Contributing code - -Introduction - -Thank you for using BIND! - -BIND is open source software that implements the Domain Name System (DNS) -protocols for the Internet. It is a reference implementation of those -protocols, but it is also production-grade software, suitable for use in -high-volume and high-reliability applications. It is by far the most -widely used DNS software, providing a robust and stable platform on top of -which organizations can build distributed computing systems with the -knowledge that those systems are fully compliant with published DNS -standards. - -BIND is and will always remain free and openly available. It can be used -and modified in any way by anyone. - -BIND is maintained by the Internet Systems Consortium, a public-benefit -501(c)(3) nonprofit, using a "managed open source" approach: anyone can -see the source, but only ISC employees have commit access. Until recently, -the source could only be seen once ISC had published a release: read -access to the source repository was restricted just as commit access was. -That's now changing, with the opening of a public git mirror to the BIND -source tree (see below). - -Access to source code - -Public BIND releases are always available from the ISC FTP site. - -A public-access GIT repository is also available at https://gitlab.isc.org -. This repository is a mirror, updated several times per day, of the -source repository maintained by ISC. It contains all the public release -branches; upcoming releases can be viewed in their current state at any -time. It does not contain development branches or unreviewed work in -progress. Commits which address security vulnerablilities are withheld -until after public disclosure. - -You can browse the source online via https://gitlab.isc.org/isc-projects/ -bind9 - -To clone the repository, use: - - $ git clone https://gitlab.isc.org/isc-projects/bind9.git - -Release branch names are of the form v9_X, where X represents the second -number in the BIND 9 version number. So, to check out the BIND 9.12 -branch, use: - - $ git checkout v9_12 - -Whenever a branch is ready for publication, a tag will be placed of the -form v9_X_Y. The 9.12.0 release, for instance, is tagged as v9_12_0. - -The branch in which the next major release is being developed is called -master. - -Reporting bugs - -Reports of flaws in the BIND package, including software bugs, errors in -the documentation, missing files in the tarball, suggested changes or -requests for new features, etc, can be filed using https://gitlab.isc.org/ -isc-projects/bind9/issues. - -Due to a large ticket backlog, we are sometimes slow to respond, -especially if a bug is cosmetic or if a feature request is vague or low in -priority, but we will try at least to acknowledge legitimate bug reports -within a week. - -ISC's ticketing system is publicly readable; however, you must have an -account to file a new issue. You can either register locally or use -credentials from an existing account at GitHub, GitLab, Google, Twitter, -or Facebook. - -Reporting possible security issues - -If you think you may be seeing a potential security vulnerability in BIND -(for example, a crash with REQUIRE, INSIST, or ASSERT failure), please -report it immediately by emailing to security-officer@isc.org. Plain-text -e-mail is not a secure choice for communications concerning undisclosed -security issues so please encrypt your communications to us if possible, -using the ISC Security Officer public key. - -Do not discuss undisclosed security vulnerabilites on any public mailing -list. ISC has a long history of handling reported vulnerabilities promptly -and effectively and we respect and acknowledge responsible reporters. - -ISC's Security Vulnerability Disclosure Policy is documented at https:// -kb.isc.org/article/AA-00861/0. - -If you have a crash, you may want to consult ?What to do if your BIND or -DHCP server has crashed.? - -Contributing code - -BIND is licensed under the Mozilla Public License 2.0. Earier versions -(BIND 9.10 and earlier) were licensed under the ISC License - -ISC does not require an explicit copyright assignment for patch -contributions. However, by submitting a patch to ISC, you implicitly -certify that you are the author of the code, that you intend to reliquish -exclusive copyright, and that you grant permission to publish your work -under the open source license used for the BIND version(s) to which your -patch will be applied. - -BIND code - -Patches for BIND may be submitted directly via merge requests in ISC's -Gitlab source repository for BIND. - -Patches can also be submitted as diffs against a specific version of BIND --- preferably the current top of the master branch. Diffs may be generated -using either git format-patch or git diff. - -Those wanting to write code for BIND may be interested in the developer -information page, which includes information about BIND design and coding -practices, including discussion of internal APIs and overall system -architecture. (This is a work in progress, and still quite preliminary.) - -Every patch submitted will be reviewed by ISC engineers following our code -review process before it is merged. - -It may take considerable time to review patch submissions, especially if -they don't meet ISC style and quality guidelines. If a patch is a good -idea, we can and will do additional work to bring it up to par, but if -we're busy with other work, it may take us a long time to get to it. - -To ensure your patch is acted on as promptly as possible, please: - - * Try to adhere to the BIND 9 coding style. - * Run make check to ensure your change hasn't caused any functional - regressions. - * Document your work, both in the patch itself and in the accompanying - email. - * In patches that make non-trivial functional changes, include system - tests if possible; when introducing or substantially altering a - library API, include unit tests. See Testing for more information. - -Changes to configure - -If you need to make changes to configure, you should not edit it directly; -instead, edit configure.in, then run autoconf. Similarly, instead of -editing config.h.in directly, edit configure.in and run autoheader. - -When submitting a patch as a diff, it's fine to omit the configure diffs -to save space. Just send the configure.in diffs and we'll generate the new -configure during the review process. - -Documentation - -All functional changes should be documented. There are three types of -documentation in the BIND source tree: - - * Man pages are kept alongside the source code for the commands they - document, in files ending in .docbook; for example, the named man page - is bin/named/named.docbook. - * The BIND 9 Administrator Reference Manual is mostly in doc/arm/ - Bv9ARM-book.xml, plus a few other XML files that are included in it. - * API documentation is in the header file describing the API, in - Doxygen-formatted comments. - -It is not necessary to edit any documentation files other than these; all -PDF, HTML, and nroff-format man page files will be updated automatically -from the docbook and XML files after merging. - -Patches to improve existing documentation are also very welcome! - -Tests - -BIND is a large and complex project. We rely heavily on continuous -automated testing and cannot merge new code without adequate test -coverage. Please see the 'Testing' section of doc/dev/dev.md for more -information. - -Thanks - -Thank you for your interest in contributing to the ongoing development of -BIND. diff --git a/OPTIONS b/OPTIONS index 340b53db67297b1dee6824d8e36a18b83b091a25..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 100644 --- a/OPTIONS +++ b/OPTIONS @@ -1,26 +0,0 @@ -Setting the STD_CDEFINES environment variable before running configure can -be used to enable certain compile-time options that are not explicitly -defined in configure. - -Some of these settings are: - -Setting Description - Overwrite memory with tag values when allocating --DISC_MEM_DEFAULTFILL=1 or freeing it; this impairs performance but - makes debugging of memory problems easier. - Don't track memory allocations by file and line --DISC_MEM_TRACKLINES=0 number; this improves performance but makes - debugging more difficult. --DISC_FACILITY=LOG_LOCAL0 Change the default syslog facility for named --DNS_CLIENT_DROPPORT=0 Disable dropping queries from particular - well-known ports: --DCHECK_SIBLING=0 Don't check sibling glue in named-checkzone --DCHECK_LOCAL=0 Don't check out-of-zone addresses in - named-checkzone --DNS_RUN_PID_DIR=0 Create default PID files in ${localstatedir}/run - rather than ${localstatedir}/run/named/ - Disable the use of inline functions to implement --DISC_BUFFER_USEINLINE=0 the isc_buffer API: this reduces performance but - may be useful when debugging --DISC_HEAP_CHECK Test heap consistency after every heap - operation; used when debugging diff --git a/README b/README index ba5f29d9f186a6d54b9a5435647fd9c2fa2adb9a..e69de29bb2d1d6434b8b29ae775ad8c2e48c5391 100644 --- a/README +++ b/README @@ -1,364 +0,0 @@ -BIND 9 - -Contents - - 1. Introduction - 2. Reporting bugs and getting help - 3. Contributing to BIND - 4. BIND 9.13 features - 5. Building BIND - 6. macOS - 7. Compile-time options - 8. Automated testing - 9. Documentation -10. Change log -11. Acknowledgments - -Introduction - -BIND (Berkeley Internet Name Domain) is a complete, highly portable -implementation of the DNS (Domain Name System) protocol. - -The BIND name server, named, is able to serve as an authoritative name -server, recursive resolver, DNS forwarder, or all three simultaneously. It -implements views for split-horizon DNS, automatic DNSSEC zone signing and -key management, catalog zones to facilitate provisioning of zone data -throughout a name server constellation, response policy zones (RPZ) to -protect clients from malicious data, response rate limiting (RRL) and -recursive query limits to reduce distributed denial of service attacks, -and many other advanced DNS features. BIND also includes a suite of -administrative tools, including the dig and delv DNS lookup tools, -nsupdate for dynamic DNS zone updates, rndc for remote name server -administration, and more. - -BIND 9 began as a complete re-write of the BIND architecture that was used -in versions 4 and 8. Internet Systems Consortium (https://www.isc.org), a -501(c)(3) public benefit corporation dedicated to providing software and -services in support of the Internet infrastructure, developed BIND 9 and -is responsible for its ongoing maintenance and improvement. BIND is open -source software licenced under the terms of the Mozilla Public License, -version 2.0. - -For a summary of features introduced in past major releases of BIND, see -the file HISTORY. - -For a detailed list of changes made throughout the history of BIND 9, see -the file CHANGES. See below for details on the CHANGES file format. - -For up-to-date release notes and errata, see http://www.isc.org/software/ -bind9/releasenotes - -For information about supported platforms, see PLATFORMS. - -Reporting bugs and getting help - -To report non-security-sensitive bugs or request new features, you may -open an Issue in the BIND 9 project on the ISC GitLab server at https:// -gitlab.isc.org/isc-projects/bind9. - -Please note that, unless you explicitly mark the newly created Issue as -"confidential", it will be publicly readable. Please do not include any -information in bug reports that you consider to be confidential unless the -issue has been marked as such. In particular, if submitting the contents -of your configuration file in a non-confidential Issue, it is advisable to -obscure key secrets: this can be done automatically by using -named-checkconf -px. - -If the bug you are reporting is a potential security issue, such as an -assertion failure or other crash in named, please do NOT use GitLab to -report it. Instead, please send mail to security-officer@isc.org. - -Professional support and training for BIND are available from ISC at -https://www.isc.org/support. - -To join the BIND Users mailing list, or view the archives, visit https:// -lists.isc.org/mailman/listinfo/bind-users. - -If you're planning on making changes to the BIND 9 source code, you may -also want to join the BIND Workers mailing list, at https://lists.isc.org/ -mailman/listinfo/bind-workers. - -Contributing to BIND - -ISC maintains a public git repository for BIND; details can be found at -http://www.isc.org/git/. - -Information for BIND contributors can be found in the following files: - -General information: CONTRIBUTING.md - BIND 9 code style: doc/dev/style.md -- BIND architecture and developer guide: doc/dev/dev.md - -Patches for BIND may be submitted as Merge Requests in the ISC GitLab -server at at https://gitlab.isc.org/isc-projects/bind9/merge_requests. - -By default, external contributors don't have ability to fork BIND in the -GitLab server, but if you wish to contribute code to BIND, you may request -permission to do so. Thereafter, you can create git branches and directly -submit requests that they be reviewed and merged. - -If you prefer, you may also submit code by opening a GitLab Issue and -including your patch as an attachment, preferably generated by git -format-patch. - -BIND 9.13 features - -BIND 9.13 is the newest development branch of BIND 9. It includes a number -of changes from BIND 9.12 and earlier releases. New features include: - - * The default value of "dnssec-validation" is now "auto". - * Support for IDNA2008 when linking with libidn2. - * "Root key sentinel" support, enabling validating resolvers to indicate - via a special query which trust anchors are configured for the root - zone. - * Secondary zones can now be configured as "mirror" zones; their - contents are transferred in as with traditional slave zones, but are - subject to DNSSEC validation and are not treated as authoritative data - when answering. This makes it easier to configure a local copy of the - root zone as described in RFC 7706. - * QNAME minimization is now supported - * The "validate-except" option allows configuration of domains below - which DNSSEC validation should not be performed. - -In addition, cryptographic support has been modernized. BIND now uses the -best available pseudo-random number generator for the platform on which -it's built. Very old versions of OpenSSL are no longer supported. -Cryptography is now mandatory; building BIND without DNSSEC is now longer -supported. - -Building BIND - -Minimally, BIND requires a UNIX or Linux system with an ANSI C compiler, -basic POSIX support, and a 64-bit integer type. Successful builds have -been observed on many versions of Linux and UNIX, including RedHat, -Fedora, Debian, Ubuntu, SuSE, Slackware, FreeBSD, NetBSD, OpenBSD, Mac OS -X, Solaris, HP-UX, AIX, SCO OpenServer, and OpenWRT. - -BIND requires a cryptography provider library such as OpenSSL or a -hardware service module supporting PKCS#11. On Linux, BIND requires the -libcap library to set process privileges, though this requirement can be -overridden by disabling capability support at compile time. See -Compile-time options below for details on other libraries that may be -required to support optional features. - -BIND is also available for Windows 2008 and higher. See win32utils/ -readme1st.txt for details on building for Windows systems. - -To build on a UNIX or Linux system, use: - - $ ./configure - $ make - -If you're planning on making changes to the BIND 9 source, you should run -make depend. If you're using Emacs, you might find make tags helpful. - -Several environment variables that can be set before running configure -will affect compilation: - -Variable Description -CC The C compiler to use. configure tries to figure out the - right one for supported systems. - C compiler flags. Defaults to include -g and/or -O2 as -CFLAGS supported by the compiler. Please include '-g' if you need - to set CFLAGS. - System header file directories. Can be used to specify -STD_CINCLUDES where add-on thread or IPv6 support is, for example. - Defaults to empty string. - Any additional preprocessor symbols you want defined. -STD_CDEFINES Defaults to empty string. For a list of possible settings, - see the file OPTIONS. -LDFLAGS Linker flags. Defaults to empty string. -BUILD_CC Needed when cross-compiling: the native C compiler to use - when building for the target system. -BUILD_CFLAGS Optional, used for cross-compiling -BUILD_CPPFLAGS -BUILD_LDFLAGS -BUILD_LIBS - -macOS - -Building on macOS assumes that the "Command Tools for Xcode" is installed. -This can be downloaded from https://developer.apple.com/download/more/ or -if you have Xcode already installed you can run "xcode-select --install". -This will add /usr/include to the system and install the compiler and -other tools so that they can be easily found. - -Compile-time options - -To see a full list of configuration options, run configure --help. - -On most platforms, BIND 9 is built with multithreading support, allowing -it to take advantage of multiple CPUs. You can configure this by -specifying --enable-threads or --disable-threads on the configure command -line. The default is to enable threads, except on some older operating -systems on which threads are known to have had problems in the past. -(Note: Prior to BIND 9.10, the default was to disable threads on Linux -systems; this has now been reversed. On Linux systems, the threaded build -is known to change BIND's behavior with respect to file permissions; it -may be necessary to specify a user with the -u option when running named.) - -To build shared libraries, specify --with-libtool on the configure command -line. - -Certain compiled-in constants and default settings can be increased to -values better suited to large servers with abundant memory resources (e.g, -64-bit servers with 12G or more of memory) by specifying --with-tuning= -large on the configure command line. This can improve performance on big -servers, but will consume more memory and may degrade performance on -smaller systems. - -For the server to support DNSSEC, you need to build it with crypto -support. To use OpenSSL, you should have OpenSSL 1.0.2e or newer -installed. If the OpenSSL library is installed in a nonstandard location, -specify the prefix using --with-openssl= on the configure command -line. To use a PKCS#11 hardware service module for cryptographic -operations, specify the path to the PKCS#11 provider library using ---with-pkcs11=, and configure BIND with --enable-native-pkcs11. - -To support the HTTP statistics channel, the server must be linked with at -least one of the following: libxml2 http://xmlsoft.org or json-c https:// -github.com/json-c. If these are installed at a nonstandard location, -specify the prefix using --with-libxml2=/prefix or --with-libjson=/prefix. - -To support compression on the HTTP statistics channel, the server must be -linked against libzlib. If this is installed in a nonstandard location, -specify the prefix using --with-zlib=/prefix. - -To support storing configuration data for runtime-added zones in an LMDB -database, the server must be linked with liblmdb. If this is installed in -a nonstandard location, specify the prefix using with-lmdb=/prefix. - -To support GeoIP location-based ACLs, the server must be linked with -libGeoIP. This is not turned on by default; BIND must be configured with ---with-geoip. If the library is installed in a nonstandard location, -specify the prefix using --with-geoip=/prefix. - -For DNSTAP packet logging, you must have installed libfstrm https:// -github.com/farsightsec/fstrm and libprotobuf-c https:// -developers.google.com/protocol-buffers, and BIND must be configured with ---enable-dnstap. - -On Linux, process capabilities are managed in user space using the libcap -library, which can be installed on most Linux systems via the libcap-dev -or libcap-devel module. Process capability support can also be disabled by -configuring with --disable-linux-caps. - -Portions of BIND that are written in Python, including dnssec-keymgr, -dnssec-coverage, dnssec-checkds, and some of the system tests, require the -'argparse' and 'ply' modules to be available. 'argparse' is a standard -module as of Python 2.7 and Python 3.2. 'ply' is available from https:// -pypi.python.org/pypi/ply. - -On some platforms it is necessary to explicitly request large file support -to handle files bigger than 2GB. This can be done by using ---enable-largefile on the configure command line. - -Support for the "fixed" rrset-order option can be enabled or disabled by -specifying --enable-fixed-rrset or --disable-fixed-rrset on the configure -command line. By default, fixed rrset-order is disabled to reduce memory -footprint. - -If your operating system has integrated support for IPv6, it will be used -automatically. If you have installed KAME IPv6 separately, use --with-kame -[=PATH] to specify its location. - -make install will install named and the various BIND 9 libraries. By -default, installation is into /usr/local, but this can be changed with the ---prefix option when running configure. - -You may specify the option --sysconfdir to set the directory where -configuration files like named.conf go by default, and --localstatedir to -set the default parent directory of run/named.pid. For backwards -compatibility with BIND 8, --sysconfdir defaults to /etc and ---localstatedir defaults to /var if no --prefix option is given. If there -is a --prefix option, sysconfdir defaults to $prefix/etc and localstatedir -defaults to $prefix/var. - -Automated testing - -A system test suite can be run with make test. The system tests require -you to configure a set of virtual IP addresses on your system (this allows -multiple servers to run locally and communicate with one another). These -IP addresses can be configured by running the command bin/tests/system/ -ifconfig.sh up as root. - -Some tests require Perl and the Net::DNS and/or IO::Socket::INET6 modules, -and will be skipped if these are not available. Some tests require Python -and the 'dnspython' module and will be skipped if these are not available. -See bin/tests/system/README for further details. - -Unit tests are implemented using Automated Testing Framework (ATF). To run -them, use configure --with-atf, then run make test or make unit. - -Documentation - -The BIND 9 Administrator Reference Manual is included with the source -distribution, in DocBook XML, HTML and PDF format, in the doc/arm -directory. - -Some of the programs in the BIND 9 distribution have man pages in their -directories. In particular, the command line options of named are -documented in bin/named/named.8. - -Frequently (and not-so-frequently) asked questions and their answers can -be found in the ISC Knowledge Base at https://kb.isc.org. - -Additional information on various subjects can be found in other README -files throughout the source tree. - -Change log - -A detailed list of all changes that have been made throughout the -development BIND 9 is included in the file CHANGES, with the most recent -changes listed first. Change notes include tags indicating the category of -the change that was made; these categories are: - -Category Description -[func] New feature -[bug] General bug fix -[security] Fix for a significant security flaw -[experimental] Used for new features when the syntax or other aspects of - the design are still in flux and may change -[port] Portability enhancement -[maint] Updates to built-in data such as root server addresses and - keys -[tuning] Changes to built-in configuration defaults and constants to - improve performance -[performance] Other changes to improve server performance -[protocol] Updates to the DNS protocol such as new RR types -[test] Changes to the automatic tests, not affecting server - functionality -[cleanup] Minor corrections and refactoring -[doc] Documentation -[contrib] Changes to the contributed tools and libraries in the - 'contrib' subdirectory - Used in the master development branch to reserve change -[placeholder] numbers for use in other branches, e.g. when fixing a bug - that only exists in older releases - -In general, [func] and [experimental] tags will only appear in new-feature -releases (i.e., those with version numbers ending in zero). Some new -functionality may be backported to older releases on a case-by-case basis. -All other change types may be applied to all currently-supported releases. - -Acknowledgments - - * The original development of BIND 9 was underwritten by the following - organizations: - - Sun Microsystems, Inc. - Hewlett Packard - Compaq Computer Corporation - IBM - Process Software Corporation - Silicon Graphics, Inc. - Network Associates, Inc. - U.S. Defense Information Systems Agency - USENIX Association - Stichting NLnet - NLnet Foundation - Nominum, Inc. - - * This product includes software developed by the OpenSSL Project for - use in the OpenSSL Toolkit. http://www.OpenSSL.org/ - * This product includes cryptographic software written by Eric Young - (eay@cryptsoft.com) - * This product includes software written by Tim Hudson - (tjh@cryptsoft.com) diff --git a/bin/check/named-checkconf.8 b/bin/check/named-checkconf.8 index 364548887e1564997c9ed04041964c215256cac4..817f1ceabf63519de28b54f82ad80c7d9ec46d4d 100644 --- a/bin/check/named-checkconf.8 +++ b/bin/check/named-checkconf.8 @@ -9,7 +9,7 @@ '\" t .\" Title: named-checkconf .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2014-01-10 .\" Manual: BIND9 .\" Source: ISC @@ -38,7 +38,7 @@ .SH "NAME" named-checkconf \- named configuration file syntax checking tool .SH "SYNOPSIS" -.HP \w'\fBnamed\-checkconf\fR\ 'u +.HP 16 \fBnamed\-checkconf\fR [\fB\-hjlvz\fR] [\fB\-p\fR\ [\fB\-x\fR\ ]] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] {filename} .SH "DESCRIPTION" .PP diff --git a/bin/check/named-checkzone.8 b/bin/check/named-checkzone.8 index 281bea4b55f32b2fac79d1fc853e9551a04eb474..159c3f6c59e57854151f19cb1a53afa017bf6f3f 100644 --- a/bin/check/named-checkzone.8 +++ b/bin/check/named-checkzone.8 @@ -9,7 +9,7 @@ '\" t .\" Title: named-checkzone .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2014-02-19 .\" Manual: BIND9 .\" Source: ISC @@ -38,9 +38,9 @@ .SH "NAME" named-checkzone, named-compilezone \- zone file validity checking or converting tool .SH "SYNOPSIS" -.HP \w'\fBnamed\-checkzone\fR\ 'u +.HP 16 \fBnamed\-checkzone\fR [\fB\-d\fR] [\fB\-h\fR] [\fB\-j\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-F\ \fR\fB\fIformat\fR\fR] [\fB\-J\ \fR\fB\fIfilename\fR\fR] [\fB\-i\ \fR\fB\fImode\fR\fR] [\fB\-k\ \fR\fB\fImode\fR\fR] [\fB\-m\ \fR\fB\fImode\fR\fR] [\fB\-M\ \fR\fB\fImode\fR\fR] [\fB\-n\ \fR\fB\fImode\fR\fR] [\fB\-l\ \fR\fB\fIttl\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-o\ \fR\fB\fIfilename\fR\fR] [\fB\-r\ \fR\fB\fImode\fR\fR] [\fB\-s\ \fR\fB\fIstyle\fR\fR] [\fB\-S\ \fR\fB\fImode\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-T\ \fR\fB\fImode\fR\fR] [\fB\-w\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-W\ \fR\fB\fImode\fR\fR] {zonename} {filename} -.HP \w'\fBnamed\-compilezone\fR\ 'u +.HP 18 \fBnamed\-compilezone\fR [\fB\-d\fR] [\fB\-j\fR] [\fB\-q\fR] [\fB\-v\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-C\ \fR\fB\fImode\fR\fR] [\fB\-f\ \fR\fB\fIformat\fR\fR] [\fB\-F\ \fR\fB\fIformat\fR\fR] [\fB\-J\ \fR\fB\fIfilename\fR\fR] [\fB\-i\ \fR\fB\fImode\fR\fR] [\fB\-k\ \fR\fB\fImode\fR\fR] [\fB\-m\ \fR\fB\fImode\fR\fR] [\fB\-n\ \fR\fB\fImode\fR\fR] [\fB\-l\ \fR\fB\fIttl\fR\fR] [\fB\-L\ \fR\fB\fIserial\fR\fR] [\fB\-r\ \fR\fB\fImode\fR\fR] [\fB\-s\ \fR\fB\fIstyle\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-T\ \fR\fB\fImode\fR\fR] [\fB\-w\ \fR\fB\fIdirectory\fR\fR] [\fB\-D\fR] [\fB\-W\ \fR\fB\fImode\fR\fR] {\fB\-o\ \fR\fB\fIfilename\fR\fR} {zonename} {filename} .SH "DESCRIPTION" .PP diff --git a/bin/delv/delv.1 b/bin/delv/delv.1 index 33311b645de342d00989f6f2b5fb7de155861c81..d981bcd6b6407d08a48f20d82a9926baceab79af 100644 --- a/bin/delv/delv.1 +++ b/bin/delv/delv.1 @@ -9,7 +9,7 @@ '\" t .\" Title: delv .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2014-04-23 .\" Manual: BIND9 .\" Source: ISC @@ -38,13 +38,13 @@ .SH "NAME" delv \- DNS lookup and validation utility .SH "SYNOPSIS" -.HP \w'\fBdelv\fR\ 'u +.HP 5 \fBdelv\fR [@server] [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-a\ \fR\fB\fIanchor\-file\fR\fR] [\fB\-b\ \fR\fB\fIaddress\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-d\ \fR\fB\fIlevel\fR\fR] [\fB\-i\fR] [\fB\-m\fR] [\fB\-p\ \fR\fB\fIport#\fR\fR] [\fB\-q\ \fR\fB\fIname\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-x\ \fR\fB\fIaddr\fR\fR] [name] [type] [class] [queryopt...] -.HP \w'\fBdelv\fR\ 'u +.HP 5 \fBdelv\fR [\fB\-h\fR] -.HP \w'\fBdelv\fR\ 'u +.HP 5 \fBdelv\fR [\fB\-v\fR] -.HP \w'\fBdelv\fR\ 'u +.HP 5 \fBdelv\fR [queryopt...] [query...] .SH "DESCRIPTION" .PP diff --git a/bin/dig/host.1 b/bin/dig/host.1 index 0bd8ff1b983c55341af465657b75127b70e04a10..ec1d41c28a246d5d34d22622dd9e6bb06e2ad87a 100644 --- a/bin/dig/host.1 +++ b/bin/dig/host.1 @@ -9,7 +9,7 @@ '\" t .\" Title: host .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2009-01-20 .\" Manual: BIND9 .\" Source: ISC @@ -38,7 +38,7 @@ .SH "NAME" host \- DNS lookup utility .SH "SYNOPSIS" -.HP \w'\fBhost\fR\ 'u +.HP 5 \fBhost\fR [\fB\-aACdlnrsTUwv\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-N\ \fR\fB\fIndots\fR\fR] [\fB\-R\ \fR\fB\fInumber\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-W\ \fR\fB\fIwait\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-v\fR] [\fB\-V\fR] {name} [server] .SH "DESCRIPTION" .PP diff --git a/bin/dig/nslookup.1 b/bin/dig/nslookup.1 index e95e3aa0b5288e65cb4f60c92bd96a2efd468406..9888a9323a6f0284ada1008892a1a1384d3fb6cf 100644 --- a/bin/dig/nslookup.1 +++ b/bin/dig/nslookup.1 @@ -9,7 +9,7 @@ '\" t .\" Title: nslookup .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2014-01-24 .\" Manual: BIND9 .\" Source: ISC @@ -38,7 +38,7 @@ .SH "NAME" nslookup \- query Internet name servers interactively .SH "SYNOPSIS" -.HP \w'\fBnslookup\fR\ 'u +.HP 9 \fBnslookup\fR [\fB\-option\fR] [name\ |\ \-] [server] .SH "DESCRIPTION" .PP @@ -85,6 +85,7 @@ nslookup \-query=hinfo \-timeout=10 .if n \{\ .RE .\} +.sp .PP The \fB\-version\fR diff --git a/bin/dnssec/dnssec-settime.8 b/bin/dnssec/dnssec-settime.8 index f71288dd0b6fb7a77d5ddffebe324b7ed4f6fb80..38ff3ca2d009212302cec05509cab6098d110564 100644 --- a/bin/dnssec/dnssec-settime.8 +++ b/bin/dnssec/dnssec-settime.8 @@ -9,7 +9,7 @@ '\" t .\" Title: dnssec-settime .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2015-08-21 .\" Manual: BIND9 .\" Source: ISC @@ -38,7 +38,7 @@ .SH "NAME" dnssec-settime \- set the key timing metadata for a DNSSEC key .SH "SYNOPSIS" -.HP \w'\fBdnssec\-settime\fR\ 'u +.HP 15 \fBdnssec\-settime\fR [\fB\-f\fR] [\fB\-K\ \fR\fB\fIdirectory\fR\fR] [\fB\-L\ \fR\fB\fIttl\fR\fR] [\fB\-P\ \fR\fB\fIdate/offset\fR\fR] [\fB\-P\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-A\ \fR\fB\fIdate/offset\fR\fR] [\fB\-R\ \fR\fB\fIdate/offset\fR\fR] [\fB\-I\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ \fR\fB\fIdate/offset\fR\fR] [\fB\-D\ sync\ \fR\fB\fIdate/offset\fR\fR] [\fB\-S\ \fR\fB\fIkey\fR\fR] [\fB\-i\ \fR\fB\fIinterval\fR\fR] [\fB\-h\fR] [\fB\-V\fR] [\fB\-v\ \fR\fB\fIlevel\fR\fR] [\fB\-E\ \fR\fB\fIengine\fR\fR] {keyfile} .SH "DESCRIPTION" .PP diff --git a/bin/named/named.8 b/bin/named/named.8 index 86df7f28e9a6c410e1d5aa6d14b25528e25233cf..d30432444ed2c8f06b61271095d0f3bc1ac613cb 100644 --- a/bin/named/named.8 +++ b/bin/named/named.8 @@ -9,7 +9,7 @@ '\" t .\" Title: named .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2014-02-19 .\" Manual: BIND9 .\" Source: ISC @@ -38,7 +38,7 @@ .SH "NAME" named \- Internet domain name server .SH "SYNOPSIS" -.HP \w'\fBnamed\fR\ 'u +.HP 6 \fBnamed\fR [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-c\ \fR\fB\fIconfig\-file\fR\fR] [\fB\-d\ \fR\fB\fIdebug\-level\fR\fR] [\fB\-D\ \fR\fB\fIstring\fR\fR] [\fB\-E\ \fR\fB\fIengine\-name\fR\fR] [\fB\-f\fR] [\fB\-g\fR] [\fB\-L\ \fR\fB\fIlogfile\fR\fR] [\fB\-M\ \fR\fB\fIoption\fR\fR] [\fB\-m\ \fR\fB\fIflag\fR\fR] [\fB\-n\ \fR\fB\fI#cpus\fR\fR] [\fB\-p\ \fR\fB\fIport\fR\fR] [\fB\-s\fR] [\fB\-S\ \fR\fB\fI#max\-socks\fR\fR] [\fB\-t\ \fR\fB\fIdirectory\fR\fR] [\fB\-U\ \fR\fB\fI#listeners\fR\fR] [\fB\-u\ \fR\fB\fIuser\fR\fR] [\fB\-v\fR] [\fB\-V\fR] [\fB\-X\ \fR\fB\fIlock\-file\fR\fR] [\fB\-x\ \fR\fB\fIcache\-file\fR\fR] .SH "DESCRIPTION" .PP @@ -164,20 +164,9 @@ Listen for queries on port Write memory usage statistics to stdout on exit\&. -.if n \{\ -.sp -.\} -.RS 4 -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.br -.ps +1 -\fBNote\fR -.ps -1 -.br +.RS +.B "Note:" This option is mainly of interest to BIND 9 developers and may be removed or changed in a future release\&. -.sp .5v .RE .RE .PP @@ -188,22 +177,11 @@ Allow to use up to \fI#max\-socks\fR sockets\&. The default value is 4096 on systems built with default configuration options, and 21000 on systems built with "configure \-\-with\-tuning=large"\&. -.if n \{\ -.sp -.\} -.RS 4 -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.br -.ps +1 -\fBWarning\fR -.ps -1 -.br +.RS +.B "Warning:" This option should be unnecessary for the vast majority of users\&. The use of this option could even be harmful because the specified value may exceed the limitation of the underlying system API\&. It is therefore set only when the default configuration causes exhaustion of file descriptors and the operational environment is known to support the specified number of sockets\&. Note also that the actual maximum number is normally a little fewer than the specified value because \fBnamed\fR reserves some file descriptors for its internal use\&. -.sp .5v .RE .RE .PP @@ -212,24 +190,13 @@ reserves some file descriptors for its internal use\&. Chroot to \fIdirectory\fR after processing the command line arguments, but before reading the configuration file\&. -.if n \{\ -.sp -.\} -.RS 4 -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.br -.ps +1 -\fBWarning\fR -.ps -1 -.br +.RS +.B "Warning:" This option should be used in conjunction with the \fB\-u\fR option, as chrooting a process running as root doesn\*(Aqt enhance security on most systems; the way \fBchroot(2)\fR is defined allows a process with root privileges to escape a chroot jail\&. -.sp .5v .RE .RE .PP @@ -251,18 +218,8 @@ may be increased as high as that value, but no higher\&. On Windows, the number Setuid to \fIuser\fR after completing privileged operations, such as creating sockets that listen on privileged ports\&. -.if n \{\ -.sp -.\} -.RS 4 -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.br -.ps +1 -\fBNote\fR -.ps -1 -.br +.RS +.B "Note:" On Linux, \fBnamed\fR uses the kernel\*(Aqs capability mechanism to drop all root privileges except the ability to @@ -273,7 +230,6 @@ option only works when \fBnamed\fR is run on kernel 2\&.2\&.18 or later, or kernel 2\&.3\&.99\-pre3 or later, since previous kernels did not allow privileges to be retained after \fBsetuid(2)\fR\&. -.sp .5v .RE .RE .PP @@ -303,20 +259,9 @@ none, the lock file check is disabled\&. Load data from \fIcache\-file\fR into the cache of the default view\&. -.if n \{\ -.sp -.\} -.RS 4 -.it 1 an-trap -.nr an-no-space-flag 1 -.nr an-break-flag 1 -.br -.ps +1 -\fBWarning\fR -.ps -1 -.br +.RS +.B "Warning:" This option must not be used\&. It is only of interest to BIND 9 developers and may be removed or changed in a future release\&. -.sp .5v .RE .RE .SH "SIGNALS" diff --git a/bin/named/named.conf.5 b/bin/named/named.conf.5 index 0f8b3ac196df62db519283aec578f41f8c65edd5..10cadaeb25e82cad8202807f341181360f6d42dc 100644 --- a/bin/named/named.conf.5 +++ b/bin/named/named.conf.5 @@ -9,13 +9,13 @@ '\" t .\" Title: named.conf .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 -.\" Date: 2018-05-29 +.\" Generator: DocBook XSL Stylesheets v1.79.1 +.\" Date: 2018-06-21 .\" Manual: BIND9 .\" Source: ISC .\" Language: English .\" -.TH "NAMED\&.CONF" "5" "2018\-05\-29" "ISC" "BIND9" +.TH "NAMED\&.CONF" "5" "2018\-06\-21" "ISC" "BIND9" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -38,7 +38,7 @@ .SH "NAME" named.conf \- configuration file for \fBnamed\fR .SH "SYNOPSIS" -.HP \w'\fBnamed\&.conf\fR\ 'u +.HP 11 \fBnamed\&.conf\fR .SH "DESCRIPTION" .PP @@ -148,7 +148,7 @@ logging { .if n \{\ .RE .\} -.SH "MANAGED-KEYS" +.SH "MANAGED\-KEYS" .sp .if n \{\ .RS 4 @@ -231,9 +231,9 @@ options { coresize ( default | unlimited | \fIsizeval\fR ); datasize ( default | unlimited | \fIsizeval\fR ); deny\-answer\-addresses { \fIaddress_match_element\fR; \&.\&.\&. } [ - except\-from { \fIquoted_string\fR; \&.\&.\&. } ]; - deny\-answer\-aliases { \fIquoted_string\fR; \&.\&.\&. } [ except\-from { - \fIquoted_string\fR; \&.\&.\&. } ]; + except\-from { \fIstring\fR; \&.\&.\&. } ]; + deny\-answer\-aliases { \fIstring\fR; \&.\&.\&. } [ except\-from { \fIstring\fR; \&.\&.\&. + } ]; dialup ( notify | notify\-passive | passive | refresh | \fIboolean\fR ); directory \fIquoted_string\fR; disable\-algorithms \fIstring\fR { \fIstring\fR; @@ -264,14 +264,12 @@ options { dnssec\-secure\-to\-insecure \fIboolean\fR; dnssec\-update\-mode ( maintain | no\-resign ); dnssec\-validation ( yes | no | auto ); - dnstap { ( all | auth | client | forwarder | - resolver ) [ ( query | response ) ]; \&.\&.\&. }; - dnstap\-identity ( \fIquoted_string\fR | none | - hostname ); - dnstap\-output ( file | unix ) \fIquoted_string\fR [ - size ( unlimited | \fIsize\fR ) ] [ versions ( - unlimited | \fIinteger\fR ) ] [ suffix ( increment - | timestamp ) ]; + dnstap { ( all | auth | client | forwarder | resolver ) [ ( query | + response ) ]; \&.\&.\&. }; + dnstap\-identity ( \fIquoted_string\fR | none | hostname ); + dnstap\-output ( file | unix ) \fIquoted_string\fR [ size ( unlimited | + \fIsize\fR ) ] [ versions ( unlimited | \fIinteger\fR ) ] [ suffix ( + increment | timestamp ) ]; dnstap\-version ( \fIquoted_string\fR | none ); dscp \fIinteger\fR; dual\-stack\-servers [ port \fIinteger\fR ] { ( \fIquoted_string\fR [ port @@ -369,7 +367,7 @@ options { preferred\-glue \fIstring\fR; prefetch \fIinteger\fR [ \fIinteger\fR ]; provide\-ixfr \fIboolean\fR; - qname\-minimization ( strict | relaxed | disabled ); + qname\-minimization ( strict | relaxed | disabled | off ); query\-source ( ( [ address ] ( \fIipv4_address\fR | * ) [ port ( \fIinteger\fR | * ) ] ) | ( [ [ address ] ( \fIipv4_address\fR | * ) ] port ( \fIinteger\fR | * ) ) ) [ dscp \fIinteger\fR ]; @@ -420,7 +418,7 @@ options { nsip\-enable \fIboolean\fR ] [ nsdname\-enable \fIboolean\fR ] [ dnsrps\-enable \fIboolean\fR ] [ dnsrps\-options { \fIunspecified\-text\fR } ]; - root\-delegation\-only [ exclude { \fIquoted_string\fR; \&.\&.\&. } ]; + root\-delegation\-only [ exclude { \fIstring\fR; \&.\&.\&. } ]; root\-key\-sentinel \fIboolean\fR; rrset\-order { [ class \fIstring\fR ] [ type \fIstring\fR ] [ name \fIquoted_string\fR ] \fIstring\fR \fIstring\fR; \&.\&.\&. }; @@ -470,6 +468,7 @@ options { use\-v4\-udp\-ports { \fIportrange\fR; \&.\&.\&. }; use\-v6\-udp\-ports { \fIportrange\fR; \&.\&.\&. }; v6\-bias \fIinteger\fR; + validate\-except { \fIstring\fR; \&.\&.\&. }; version ( \fIquoted_string\fR | none ); zero\-no\-soa\-ttl \fIboolean\fR; zero\-no\-soa\-ttl\-cache \fIboolean\fR; @@ -521,7 +520,7 @@ server \fInetprefix\fR { .if n \{\ .RE .\} -.SH "STATISTICS-CHANNELS" +.SH "STATISTICS\-CHANNELS" .sp .if n \{\ .RS 4 @@ -537,7 +536,7 @@ statistics\-channels { .if n \{\ .RE .\} -.SH "TRUSTED-KEYS" +.SH "TRUSTED\-KEYS" .sp .if n \{\ .RS 4 @@ -597,9 +596,9 @@ view \fIstring\fR [ \fIclass\fR ] { cleaning\-interval \fIinteger\fR; clients\-per\-query \fIinteger\fR; deny\-answer\-addresses { \fIaddress_match_element\fR; \&.\&.\&. } [ - except\-from { \fIquoted_string\fR; \&.\&.\&. } ]; - deny\-answer\-aliases { \fIquoted_string\fR; \&.\&.\&. } [ except\-from { - \fIquoted_string\fR; \&.\&.\&. } ]; + except\-from { \fIstring\fR; \&.\&.\&. } ]; + deny\-answer\-aliases { \fIstring\fR; \&.\&.\&. } [ except\-from { \fIstring\fR; \&.\&.\&. + } ]; dialup ( notify | notify\-passive | passive | refresh | \fIboolean\fR ); disable\-algorithms \fIstring\fR { \fIstring\fR; \&.\&.\&. }; @@ -633,8 +632,8 @@ view \fIstring\fR [ \fIclass\fR ] { dnssec\-secure\-to\-insecure \fIboolean\fR; dnssec\-update\-mode ( maintain | no\-resign ); dnssec\-validation ( yes | no | auto ); - dnstap { ( all | auth | client | forwarder | - resolver ) [ ( query | response ) ]; \&.\&.\&. }; + dnstap { ( all | auth | client | forwarder | resolver ) [ ( query | + response ) ]; \&.\&.\&. }; dual\-stack\-servers [ port \fIinteger\fR ] { ( \fIquoted_string\fR [ port \fIinteger\fR ] [ dscp \fIinteger\fR ] | \fIipv4_address\fR [ port \fIinteger\fR ] [ dscp \fIinteger\fR ] | \fIipv6_address\fR [ port @@ -712,7 +711,7 @@ view \fIstring\fR [ \fIclass\fR ] { preferred\-glue \fIstring\fR; prefetch \fIinteger\fR [ \fIinteger\fR ]; provide\-ixfr \fIboolean\fR; - qname\-minimization ( strict | relaxed | disabled ); + qname\-minimization ( strict | relaxed | disabled | off ); query\-source ( ( [ address ] ( \fIipv4_address\fR | * ) [ port ( \fIinteger\fR | * ) ] ) | ( [ [ address ] ( \fIipv4_address\fR | * ) ] port ( \fIinteger\fR | * ) ) ) [ dscp \fIinteger\fR ]; @@ -758,7 +757,7 @@ view \fIstring\fR [ \fIclass\fR ] { nsip\-enable \fIboolean\fR ] [ nsdname\-enable \fIboolean\fR ] [ dnsrps\-enable \fIboolean\fR ] [ dnsrps\-options { \fIunspecified\-text\fR } ]; - root\-delegation\-only [ exclude { \fIquoted_string\fR; \&.\&.\&. } ]; + root\-delegation\-only [ exclude { \fIstring\fR; \&.\&.\&. } ]; root\-key\-sentinel \fIboolean\fR; rrset\-order { [ class \fIstring\fR ] [ type \fIstring\fR ] [ name \fIquoted_string\fR ] \fIstring\fR \fIstring\fR; \&.\&.\&. }; @@ -820,6 +819,7 @@ view \fIstring\fR [ \fIclass\fR ] { update\-check\-ksk \fIboolean\fR; use\-alt\-transfer\-source \fIboolean\fR; v6\-bias \fIinteger\fR; + validate\-except { \fIstring\fR; \&.\&.\&. }; zero\-no\-soa\-ttl \fIboolean\fR; zero\-no\-soa\-ttl\-cache \fIboolean\fR; zone \fIstring\fR [ \fIclass\fR ] { @@ -901,7 +901,7 @@ view \fIstring\fR [ \fIclass\fR ] { serial\-update\-method ( date | increment | unixtime ); server\-addresses { ( \fIipv4_address\fR | \fIipv6_address\fR ) [ port \fIinteger\fR ]; \&.\&.\&. }; - server\-names { \fIquoted_string\fR; \&.\&.\&. }; + server\-names { \fIstring\fR; \&.\&.\&. }; sig\-signing\-nodes \fIinteger\fR; sig\-signing\-signatures \fIinteger\fR; sig\-signing\-type \fIinteger\fR; @@ -1009,7 +1009,7 @@ zone \fIstring\fR [ \fIclass\fR ] { serial\-update\-method ( date | increment | unixtime ); server\-addresses { ( \fIipv4_address\fR | \fIipv6_address\fR ) [ port \fIinteger\fR ]; \&.\&.\&. }; - server\-names { \fIquoted_string\fR; \&.\&.\&. }; + server\-names { \fIstring\fR; \&.\&.\&. }; sig\-signing\-nodes \fIinteger\fR; sig\-signing\-signatures \fIinteger\fR; sig\-signing\-type \fIinteger\fR; diff --git a/bin/named/named.conf.html b/bin/named/named.conf.html index 1184de56fdb8c5a61c264c3a9992ba2ce6ecb6bc..bd61e0f951dcd93ba8e26532f880a2847d33adea 100644 --- a/bin/named/named.conf.html +++ b/bin/named/named.conf.html @@ -10,65 +10,46 @@ named.conf - +
- - - - - -
+

Name

-

- named.conf - — configuration file for named -

+

named.conf — configuration file for named

- - - -
+

Synopsis

-

- named.conf -

-
- -
+

named.conf

+
+

DESCRIPTION

- -

named.conf is the configuration file +

named.conf is the configuration file for named. Statements are enclosed in braces and terminated with a semi-colon. Clauses in the statements are also semi-colon terminated. The usual comment styles are supported:

-

+

C style: /* */

-

+

C++ style: // to end of line

-

+

Unix style: # to end of line

-
- -
+
+

ACL

- -


+


acl string { address_match_element; ... };

-
- -
+
+

CONTROLS

- -


+


controls {
inet ( ipv4_address | ipv6_address |
    * ) [ port ( integer | * ) ] allow
@@ -81,43 +62,35 @@ controls     boolean ];
};

-
- -
+
+

DLZ

- -


+


dlz string {
database string;
search boolean;
};

-
- -
+
+

DYNDB

- -


+


dyndb string quoted_string {
    unspecified-text };

-
- -
+
+

KEY

- -


+


key string {
algorithm string;
secret string;
};

-
- -
+
+

LOGGING

- -


+


logging {
category string { string; ... };
channel string {
@@ -134,33 +107,26 @@ logging };
};

-
- - -
+
+

MANAGED-KEYS

- -


+


managed-keys { string string integer
    integer integer quoted_string; ... };

-
- -
+
+

MASTERS

- -


+


masters string [ port integer ] [ dscp
    integer ] { ( masters | ipv4_address [
    port integer ] | ipv6_address [ port
    integer ] ) [ key string ]; ... };

-
- -
+
+

OPTIONS

- -


+


options {
allow-new-zones boolean;
allow-notify { address_match_element; ... };
@@ -212,9 +178,9 @@ options coresize ( default | unlimited | sizeval );
datasize ( default | unlimited | sizeval );
deny-answer-addresses { address_match_element; ... } [
-     except-from { quoted_string; ... } ];
- deny-answer-aliases { quoted_string; ... } [ except-from {
-     quoted_string; ... } ];
+     except-from { string; ... } ];
+ deny-answer-aliases { string; ... } [ except-from { string; ...
+     } ];
dialup ( notify | notify-passive | passive | refresh | boolean );
directory quoted_string;
disable-algorithms string { string;
@@ -245,14 +211,12 @@ options dnssec-secure-to-insecure boolean;
dnssec-update-mode ( maintain | no-resign );
dnssec-validation ( yes | no | auto );
- dnstap { ( all | auth | client | forwarder |
-     resolver ) [ ( query | response ) ]; ... };
- dnstap-identity ( quoted_string | none |
-     hostname );
- dnstap-output ( file | unix ) quoted_string [
-     size ( unlimited | size ) ] [ versions (
-     unlimited | integer ) ] [ suffix ( increment
-     | timestamp ) ];
+ dnstap { ( all | auth | client | forwarder | resolver ) [ ( query |
+     response ) ]; ... };
+ dnstap-identity ( quoted_string | none | hostname );
+ dnstap-output ( file | unix ) quoted_string [ size ( unlimited |
+     size ) ] [ versions ( unlimited | integer ) ] [ suffix (
+     increment | timestamp ) ];
dnstap-version ( quoted_string | none );
dscp integer;
dual-stack-servers [ port integer ] { ( quoted_string [ port
@@ -350,7 +314,7 @@ options preferred-glue string;
prefetch integer [ integer ];
provide-ixfr boolean;
- qname-minimization ( strict | relaxed | disabled );
+ qname-minimization ( strict | relaxed | disabled | off );
query-source ( ( [ address ] ( ipv4_address | * ) [ port (
    integer | * ) ] ) | ( [ [ address ] ( ipv4_address | * ) ]
    port ( integer | * ) ) ) [ dscp integer ];
@@ -401,7 +365,7 @@ options     nsip-enable boolean ] [ nsdname-enable boolean ] [
    dnsrps-enable boolean ] [ dnsrps-options { unspecified-text
    } ];
- root-delegation-only [ exclude { quoted_string; ... } ];
+ root-delegation-only [ exclude { string; ... } ];
root-key-sentinel boolean;
rrset-order { [ class string ] [ type string ] [ name
    quoted_string ] string string; ... };
@@ -451,18 +415,17 @@ options use-v4-udp-ports { portrange; ... };
use-v6-udp-ports { portrange; ... };
v6-bias integer;
+ validate-except { string; ... };
version ( quoted_string | none );
zero-no-soa-ttl boolean;
zero-no-soa-ttl-cache boolean;
zone-statistics ( full | terse | none | boolean );
};

-
- -
+
+

SERVER

- -


+


server netprefix {
bogus boolean;
edns boolean;
@@ -496,12 +459,10 @@ server transfers integer;
};

-
- -
+
+

STATISTICS-CHANNELS

- -


+


statistics-channels {
inet ( ipv4_address | ipv6_address |
    * ) [ port ( integer | * ) ] [
@@ -509,21 +470,17 @@ statistics-channels     } ];
};

-
- -
+
+

TRUSTED-KEYS

- -


+


trusted-keys { string integer integer
    integer quoted_string; ... };

-
- -
+
+

VIEW

- -


+


view string [ class ] {
allow-new-zones boolean;
allow-notify { address_match_element; ... };
@@ -566,9 +523,9 @@ view cleaning-interval integer;
clients-per-query integer;
deny-answer-addresses { address_match_element; ... } [
-     except-from { quoted_string; ... } ];
- deny-answer-aliases { quoted_string; ... } [ except-from {
-     quoted_string; ... } ];
+     except-from { string; ... } ];
+ deny-answer-aliases { string; ... } [ except-from { string; ...
+     } ];
dialup ( notify | notify-passive | passive | refresh | boolean );
disable-algorithms string { string;
    ... };
@@ -602,8 +559,8 @@ view dnssec-secure-to-insecure boolean;
dnssec-update-mode ( maintain | no-resign );
dnssec-validation ( yes | no | auto );
- dnstap { ( all | auth | client | forwarder |
-     resolver ) [ ( query | response ) ]; ... };
+ dnstap { ( all | auth | client | forwarder | resolver ) [ ( query |
+     response ) ]; ... };
dual-stack-servers [ port integer ] { ( quoted_string [ port
    integer ] [ dscp integer ] | ipv4_address [ port
    integer ] [ dscp integer ] | ipv6_address [ port
@@ -681,7 +638,7 @@ view preferred-glue string;
prefetch integer [ integer ];
provide-ixfr boolean;
- qname-minimization ( strict | relaxed | disabled );
+ qname-minimization ( strict | relaxed | disabled | off );
query-source ( ( [ address ] ( ipv4_address | * ) [ port (
    integer | * ) ] ) | ( [ [ address ] ( ipv4_address | * ) ]
    port ( integer | * ) ) ) [ dscp integer ];
@@ -727,7 +684,7 @@ view     nsip-enable boolean ] [ nsdname-enable boolean ] [
    dnsrps-enable boolean ] [ dnsrps-options { unspecified-text
    } ];
- root-delegation-only [ exclude { quoted_string; ... } ];
+ root-delegation-only [ exclude { string; ... } ];
root-key-sentinel boolean;
rrset-order { [ class string ] [ type string ] [ name
    quoted_string ] string string; ... };
@@ -789,6 +746,7 @@ view update-check-ksk boolean;
use-alt-transfer-source boolean;
v6-bias integer;
+ validate-except { string; ... };
zero-no-soa-ttl boolean;
zero-no-soa-ttl-cache boolean;
zone string [ class ] {
@@ -870,7 +828,7 @@ view serial-update-method ( date | increment | unixtime );
server-addresses { ( ipv4_address | ipv6_address ) [
    port integer ]; ... };
- server-names { quoted_string; ... };
+ server-names { string; ... };
sig-signing-nodes integer;
sig-signing-signatures integer;
sig-signing-type integer;
@@ -896,12 +854,10 @@ view zone-statistics ( full | terse | none | boolean );
};

-
- -
+
+

ZONE

- -


+


zone string [ class ] {
allow-notify { address_match_element; ... };
allow-query { address_match_element; ... };
@@ -975,7 +931,7 @@ zone serial-update-method ( date | increment | unixtime );
server-addresses { ( ipv4_address | ipv6_address ) [ port
    integer ]; ... };
- server-names { quoted_string; ... };
+ server-names { string; ... };
sig-signing-nodes integer;
sig-signing-signatures integer;
sig-signing-type integer;
@@ -997,36 +953,21 @@ zone zone-statistics ( full | terse | none | boolean );
};

-
- -
+
+

FILES

- -

/etc/named.conf +

/etc/named.conf

-
- -
+
+

SEE ALSO

- -

- ddns-confgen(8) - , - - named(8) - , - - named-checkconf(8) - , - - rndc(8) - , - - rndc-confgen(8) - , +

ddns-confgen(8), + named(8), + named-checkconf(8), + rndc(8), + rndc-confgen(8), BIND 9 Administrator Reference Manual.

-
- +
diff --git a/bin/nsupdate/nsupdate.1 b/bin/nsupdate/nsupdate.1 index 2706fef8fd53624a074ecb72b9507e896d82a6f0..489716a08154004517557b9b2a612090053e396e 100644 --- a/bin/nsupdate/nsupdate.1 +++ b/bin/nsupdate/nsupdate.1 @@ -9,7 +9,7 @@ '\" t .\" Title: nsupdate .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2014-04-18 .\" Manual: BIND9 .\" Source: ISC @@ -38,7 +38,7 @@ .SH "NAME" nsupdate \- Dynamic DNS update utility .SH "SYNOPSIS" -.HP \w'\fBnsupdate\fR\ 'u +.HP 9 \fBnsupdate\fR [\fB\-d\fR] [\fB\-D\fR] [\fB\-i\fR] [\fB\-L\ \fR\fB\fIlevel\fR\fR] [[\fB\-g\fR] | [\fB\-o\fR] | [\fB\-l\fR] | [\fB\-y\ \fR\fB\fI[hmac:]\fR\fIkeyname:secret\fR\fR] | [\fB\-k\ \fR\fB\fIkeyfile\fR\fR]] [\fB\-t\ \fR\fB\fItimeout\fR\fR] [\fB\-u\ \fR\fB\fIudptimeout\fR\fR] [\fB\-r\ \fR\fB\fIudpretries\fR\fR] [\fB\-v\fR] [\fB\-T\fR] [\fB\-P\fR] [\fB\-V\fR] [[\fB\-4\fR] | [\fB\-6\fR]] [filename] .SH "DESCRIPTION" .PP @@ -286,7 +286,8 @@ will clear the default ttl\&. \fBkey\fR [hmac:] {keyname} {secret} .RS 4 Specifies that all updates are to be TSIG\-signed using the -\fIkeyname\fR\fIsecret\fR +\fIkeyname\fR +\fIsecret\fR pair\&. If \fIhmac\fR is specified, then it sets the signing algorithm in use; the default is diff --git a/bin/tools/mdig.1 b/bin/tools/mdig.1 index 5f7658d330754bb2ec910c38cac3cacf59e3c14f..33d721d9e3c7e82bc1fd90eb0646098f9a993432 100644 --- a/bin/tools/mdig.1 +++ b/bin/tools/mdig.1 @@ -9,7 +9,7 @@ '\" t .\" Title: mdig .\" Author: -.\" Generator: DocBook XSL Stylesheets v1.78.1 +.\" Generator: DocBook XSL Stylesheets v1.79.1 .\" Date: 2015-01-05 .\" Manual: BIND9 .\" Source: ISC @@ -38,11 +38,11 @@ .SH "NAME" mdig \- DNS pipelined lookup utility .SH "SYNOPSIS" -.HP \w'\fBmdig\fR\ 'u +.HP 5 \fBmdig\fR {@server} [\fB\-f\ \fR\fB\fIfilename\fR\fR] [\fB\-h\fR] [\fB\-v\fR] [[\fB\-4\fR] | [\fB\-6\fR]] [\fB\-m\fR] [\fB\-b\ \fR\fB\fIaddress\fR\fR] [\fB\-p\ \fR\fB\fIport#\fR\fR] [\fB\-c\ \fR\fB\fIclass\fR\fR] [\fB\-t\ \fR\fB\fItype\fR\fR] [\fB\-i\fR] [\fB\-x\ \fR\fB\fIaddr\fR\fR] [plusopt...] -.HP \w'\fBmdig\fR\ 'u +.HP 5 \fBmdig\fR {\-h} -.HP \w'\fBmdig\fR\ 'u +.HP 5 \fBmdig\fR [@server] {global\-opt...} {{local\-opt...}\ {query}...} .SH "DESCRIPTION" .PP diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index 68b02ecf99100f6c91f47bc1882f2709af07d2d9..9333c2c5321e0f0805aedecd10ea30b947be0217 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -10,7 +10,7 @@ Chapter 1. Introduction - + @@ -50,8 +50,7 @@
- -

+

The Internet Domain Name System (DNS) consists of the syntax to specify the names of entities in the Internet in a hierarchical @@ -61,12 +60,10 @@ group of distributed hierarchical databases.

- -
+

Scope of Document

- -

+

The Berkeley Internet Name Domain (BIND) implements a domain name server for a number of operating systems. This @@ -75,14 +72,12 @@ BIND version 9 software package for system administrators.

-

This version of the manual corresponds to BIND version 9.13.

-
- -
+

This version of the manual corresponds to BIND version 9.13.

+
+

Organization of This Document

- -

+

In this document, Chapter 1 introduces the basic DNS and BIND concepts. Chapter 2 describes resource requirements for running BIND in various @@ -105,18 +100,15 @@ and the Domain Name System.

-
-
+
+

Conventions Used in This Document

- -

+

In this document, we use the following general typographic conventions:

- -
- +
@@ -173,14 +165,11 @@ -
-
- -

+

+

The following conventions are used in descriptions of the BIND configuration file:

-
- +
@@ -235,36 +224,31 @@ -
-
+

-
-
+
+

The Domain Name System (DNS)

- -

+

The purpose of this document is to explain the installation and upkeep of the BIND (Berkeley Internet Name Domain) software package, and we begin by reviewing the fundamentals of the Domain Name System (DNS) as they relate to BIND.

- -
+

DNS Fundamentals

- -

+

The Domain Name System (DNS) is a hierarchical, distributed database. It stores information for mapping Internet host names to IP addresses and vice versa, mail routing information, and other data used by Internet applications.

- -

+

Clients look up information in the DNS by calling a resolver library, which sends queries to one or more name servers and interprets the responses. @@ -272,13 +256,11 @@ contains a name server, named, and a set of associated tools.

- -
-
+
+

Domains and Domain Names

- -

+

The data stored in the DNS is identified by domain names that are organized as a tree according to organizational or administrative boundaries. Each node of the tree, called a domain, is given a label. The domain @@ -289,8 +271,7 @@ separated by dots. A label need only be unique within its parent domain.

- -

+

For example, a domain name for a host at the company Example, Inc. could be ourhost.example.com, @@ -302,8 +283,7 @@ ourhost is the name of the host.

- -

+

For administrative purposes, the name space is partitioned into areas called zones, each starting at a node and extending down to the leaf nodes or to nodes where other zones @@ -311,32 +291,27 @@ The data for each zone is stored in a name server, which answers queries about the zone using the DNS protocol.

- -

+

The data associated with each domain name is stored in the form of resource records (RRs). Some of the supported resource record types are described in the section called “Types of Resource Records and When to Use Them”.

- -

+

For more detailed information about the design of the DNS and the DNS protocol, please refer to the standards documents listed in the section called “Request for Comments (RFCs)”.

-
- -
+
+

Zones

- -

+

To properly operate a name server, it is important to understand the difference between a zone and a domain.

- -

+

As stated previously, a zone is a point of delegation in the DNS tree. A zone consists of those contiguous parts of the domain @@ -348,8 +323,7 @@ parent zone, which should be matched by equivalent NS records at the root of the delegated zone.

- -

+

For instance, consider the example.com domain which includes names such as host.aaa.example.com and @@ -371,8 +345,7 @@ gain a complete understanding of this difficult and subtle topic.

- -

+

Though BIND is called a "domain name server", it deals primarily in terms of zones. The master and slave @@ -382,13 +355,11 @@ be a slave server for your domain, you are actually asking for slave service for some collection of zones.

-
- -
+
+

Authoritative Name Servers

- -

+

Each zone is served by at least one authoritative name server, which contains the complete data for the zone. @@ -396,19 +367,16 @@ most zones have two or more authoritative servers, on different networks.

- -

+

Responses from authoritative servers have the "authoritative answer" (AA) bit set in the response packets. This makes them easy to identify when debugging DNS configurations using tools like dig (the section called “Diagnostic Tools”).

- -
+

The Primary Master

- -

+

The authoritative server where the master copy of the zone data is maintained is called the primary master server, or simply the @@ -419,19 +387,16 @@ zone file or master file.

- -

+

In some cases, however, the master file may not be edited by humans at all, but may instead be the result of dynamic update operations.

-
- -
+
+

Slave Servers

- -

+

The other authoritative servers, the slave servers (also known as secondary servers) load the zone contents from another server using a replication @@ -441,7 +406,7 @@ slave. In other words, a slave server may itself act as a master to a subordinate slave server.

-

+

Periodically, the slave server must send a refresh query to determine whether the zone contents have been updated. This is done by sending a query for the zone's SOA record and @@ -454,19 +419,17 @@ max-retry-time, and min-retry-time options.

-

+

If the zone data cannot be updated within the time specified by the SOA EXPIRE option (up to a hard-coded maximum of 24 weeks) then the slave zone expires and will no longer respond to queries.

-
- -
+
+

Stealth Servers

- -

+

Usually all of the zone's authoritative servers are listed in NS records in the parent zone. These NS records constitute a delegation of the zone from the parent. @@ -477,8 +440,7 @@ list servers in the parent's delegation that are not present at the zone's top level.

- -

+

A stealth server is a server that is authoritative for a zone but is not listed in that zone's NS records. Stealth servers can be used for keeping a local copy of @@ -489,8 +451,7 @@ are inaccessible.

- -

+

A configuration where the primary master server itself is a stealth server is often referred to as a "hidden primary" configuration. One use for this configuration is when the primary @@ -498,17 +459,12 @@ is behind a firewall and therefore unable to communicate directly with the outside world.

- -
- -
-
+
+
+

Caching Name Servers

- - - -

+

The resolver libraries provided by most operating systems are stub resolvers, meaning that they are not capable of @@ -520,26 +476,22 @@ is called a recursive name server; it performs recursive lookups for local clients.

- -

+

To improve performance, recursive servers cache the results of the lookups they perform. Since the processes of recursion and caching are intimately connected, the terms recursive server and caching server are often used synonymously.

- -

+

The length of time for which a record may be retained in the cache of a caching name server is controlled by the Time To Live (TTL) field associated with each resource record.

- -
+

Forwarding

- -

+

Even a caching name server does not necessarily perform the complete recursive lookup itself. Instead, it can forward some or all of the queries @@ -547,8 +499,7 @@ server, commonly referred to as a forwarder.

- -

+

There may be one or more forwarders, and they are queried in turn until the list is exhausted or an answer @@ -562,22 +513,18 @@ that can do it, and that server would query the Internet DNS servers on the internal server's behalf.

-
- -
- -
+
+
+

Name Servers in Multiple Roles

- -

+

The BIND name server can simultaneously act as a master for some zones, a slave for other zones, and as a caching (recursive) server for a set of local clients.

- -

+

However, since the functions of authoritative name service and caching/recursive name service are logically separate, it is often advantageous to run them on separate server machines. @@ -592,11 +539,9 @@ does not need to be reachable from the Internet at large and can be placed inside a firewall.

- -
-
- -
+
+
+
@@ -614,6 +559,6 @@
-

BIND 9.13.2 (Development Release)

+

BIND 9.13.3-dev (Development Release)

diff --git a/doc/arm/Bv9ARM.ch02.html b/doc/arm/Bv9ARM.ch02.html index 7862592500ba251d227101e6aa77969235cb2bb2..1e7e2084314a4ce93a872aa70d28d8cc5195fce8 100644 --- a/doc/arm/Bv9ARM.ch02.html +++ b/doc/arm/Bv9ARM.ch02.html @@ -10,7 +10,7 @@ Chapter 2. BIND Resource Requirements - + @@ -43,17 +43,16 @@
Supported Operating Systems
- -
+

Hardware requirements

-

+

DNS hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from active duty have performed admirably as DNS servers.

-

+

The DNSSEC features of BIND 9 may prove to be quite CPU intensive however, so organizations that make heavy use of these @@ -62,22 +61,22 @@ full utilization of multiprocessor systems for installations that need it.

-
-
+
+

CPU Requirements

-

+

CPU requirements for BIND 9 range from i486-class machines for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC signed zones, serving many thousands of queries per second.

-
-
+
+

Memory Requirements

-

+

The memory of the server has to be large enough to fit the cache and zones loaded off disk. The max-cache-size option can be used to limit the amount of memory used by the cache, @@ -91,14 +90,11 @@ a relatively stable size where entries are expiring from the cache as fast as they are being inserted.

- -
- -
+
+

Name Server Intensive Environment Issues

- -

+

For name server intensive environments, there are two alternative configurations that may be used. The first is where clients and any second-level internal name servers query a main name server, which @@ -111,13 +107,11 @@ this has the disadvantage of making many more external queries, as none of the name servers share their cached data.

-
- -
+
+

Supported Operating Systems

- -

+

ISC BIND 9 compiles and runs on a large number of Unix-like operating systems and on @@ -127,8 +121,8 @@ directory of the BIND 9 source distribution.

-
-
+
+
@@ -146,6 +140,6 @@
-

BIND 9.13.2 (Development Release)

+

BIND 9.13.3-dev (Development Release)

diff --git a/doc/arm/Bv9ARM.ch03.html b/doc/arm/Bv9ARM.ch03.html index c78f599122223f51f9a7ad4aa6e493698cebc681..9879c9dffd7bfc9c9a839deabd26b7a077a87c44 100644 --- a/doc/arm/Bv9ARM.ch03.html +++ b/doc/arm/Bv9ARM.ch03.html @@ -10,7 +10,7 @@ Chapter 3. Name Server Configuration - + @@ -49,22 +49,18 @@
- -

+

In this chapter we provide some suggested configurations along with guidelines for their use. We suggest reasonable values for certain option settings.

- -
+

Sample Configurations

- -
+

A Caching-only Name Server

- -

+

The following sample configuration is appropriate for a caching-only name server for use by clients internal to a corporation. All queries @@ -73,7 +69,6 @@ suitable firewall rules.

- 
 // Two corporate subnets we wish to allow queries from.
 acl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
@@ -91,19 +86,15 @@ zone "0.0.127.in-addr.arpa" {
      notify no;
 };
- -
- -
+
+

An Authoritative-only Name Server

- -

+

This sample configuration is for an authoritative-only server that is the master server for "example.com" and a slave for the subdomain "eng.example.com".

- 
 options {
      // Working directory
@@ -142,31 +133,23 @@ zone "eng.example.com" {
      masters { 192.168.4.12; };
 };
- -
-
- -
+
+
+

Load Balancing

- - - -

+

A primitive form of load balancing can be achieved in the DNS by using multiple records (such as multiple A records) for one name.

- -

+

For example, if you have three WWW servers with network addresses of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the following means that clients will connect to each machine one third of the time:

- -
- +
@@ -280,52 +263,47 @@ zone "eng.example.com" { -
-
-

+

+

When a resolver queries for these records, BIND will rotate them and respond to the query with the records in a different order. In the example above, clients will randomly receive records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients will use the first record returned and discard the rest.

-

+

For more detail on ordering responses, check the rrset-order sub-statement in the options statement, see RRset Ordering.

- -
- -
+
+

Name Server Operations

- -
+

Tools for Use With the Name Server Daemon

-

+

This section describes several indispensable diagnostic, administrative and monitoring tools available to the system administrator for controlling and debugging the name server daemon.

-
+

Diagnostic Tools

-

+

The dig, host, and nslookup programs are all command line tools for manually querying name servers. They differ in style and output format.

- -
+
dig
-

+

dig is the most versatile and complete of these lookup tools. It has two modes: simple interactive @@ -335,31 +313,22 @@ zone "eng.example.com" { accessible from the command line.

-

- dig - [@server] - domain - [query-type] - [query-class] - [+query-option] - [-dig-option] - [%comment] -

-

+

dig [@server] domain [query-type] [query-class] [+query-option] [-dig-option] [%comment]

+

The usual simple use of dig will take the form

-

+

dig @server domain query-type query-class

-

+

For more information and a list of available commands and options, see the dig man page.

-
+
host
-

+

The host utility emphasizes simplicity and ease of use. By default, it converts @@ -367,29 +336,16 @@ zone "eng.example.com" { functionality can be extended with the use of options.

-

- host - [-aCdlnrsTwv] - [-c class] - [-N ndots] - [-t type] - [-W timeout] - [-R retries] - [-m flag] - [-4] - [-6] - hostname - [server] -

-

+

host [-aCdlnrsTwv] [-c class] [-N ndots] [-t type] [-W timeout] [-R retries] [-m flag] [-4] [-6] hostname [server]

+

For more information and a list of available commands and options, see the host man page.

-
+
nslookup
-

nslookup +

nslookup has two modes: interactive and non-interactive. Interactive mode allows the user to query name servers for information about various @@ -398,15 +354,8 @@ zone "eng.example.com" { the name and requested information for a host or domain.

-

- nslookup - [-option...] - [ - [host-to-find] - | [- [server]] - ] -

-

+

nslookup [-option...] [[host-to-find] | [- [server]]]

+

Interactive mode is entered when no arguments are given (the default name server will be used) or when the first argument is a @@ -414,7 +363,7 @@ zone "eng.example.com" { Internet address of a name server.

-

+

Non-interactive mode is used when the name or Internet address of the host to be looked up is given as the first argument. @@ -422,76 +371,56 @@ zone "eng.example.com" { optional second argument specifies the host name or address of a name server.

-

+

Due to its arcane user interface and frequently inconsistent behavior, we do not recommend the use of nslookup. Use dig instead.

-
+
-
- -
+
+

Administrative Tools

-

+

Administrative tools play an integral part in the management of a server.

-
+
named-checkconf
-

+

The named-checkconf program checks the syntax of a named.conf file.

-

- named-checkconf - [-jvz] - [-t directory] - [filename] -

-
+

named-checkconf [-jvz] [-t directory] [filename]

+
named-checkzone
-

+

The named-checkzone program checks a master file for syntax and consistency.

-

- named-checkzone - [-djqvD] - [-c class] - [-o output] - [-t directory] - [-w directory] - [-k (ignore|warn|fail)] - [-n (ignore|warn|fail)] - [-W (ignore|warn)] - zone - [filename] -

-
+

named-checkzone [-djqvD] [-c class] [-o output] [-t directory] [-w directory] [-k (ignore|warn|fail)] [-n (ignore|warn|fail)] [-W (ignore|warn)] zone [filename]

+
named-compilezone
-
-

+

Similar to named-checkzone, but it always dumps the zone content to a specified file (typically in a different format). -

-
+

rndc
-

+

The remote name daemon control (rndc) program allows the system @@ -506,21 +435,11 @@ zone "eng.example.com" { options it will display a usage message as follows:

-

- rndc - [-c config] - [-s server] - [-p port] - [-y key] - command - [command...] -

- -

See rndc(8) for details of +

rndc [-c config] [-s server] [-p port] [-y key] command [command...]

+

See rndc(8) for details of the available rndc commands.

- -

+

rndc requires a configuration file, since all communication with the server is authenticated with @@ -544,8 +463,7 @@ zone "eng.example.com" { the section called “controls Statement Definition and Usage”.

- -

+

The format of the configuration file is similar to that of named.conf, but limited to @@ -557,8 +475,7 @@ zone "eng.example.com" { be shared. The order of statements is not significant.

- -

+

The options statement has three clauses: default-server, default-key, @@ -576,8 +493,7 @@ zone "eng.example.com" { port is given on the command line or in a server statement.

- -

+

The key statement defines a key to be used by rndc when authenticating @@ -606,8 +522,7 @@ zone "eng.example.com" { have any meaning. The secret is a Base64 encoded string as specified in RFC 3548.

- -

+

The server statement associates a key defined using the key @@ -623,11 +538,9 @@ zone "eng.example.com" { connect to on the server.

- -

+

A sample minimal configuration file is as follows:

- 
 key rndc_key {
      algorithm "hmac-sha256";
@@ -639,36 +552,30 @@ options {
      default-key    rndc_key;
 };
- -

+

This file, if installed as /etc/rndc.conf, would allow the command:

- -

+

$ rndc reload

- -

+

to connect to 127.0.0.1 port 953 and cause the name server to reload, if a name server on the local machine were running with following controls statements:

- 
 controls {
         inet 127.0.0.1
             allow { localhost; } keys { rndc_key; };
 };
- -

+

and it had an identical key statement for rndc_key.

- -

+

Running the rndc-confgen program will conveniently create a rndc.conf @@ -683,23 +590,19 @@ controls { modify named.conf at all.

- -
+
- -
-
- -
+
+
+

Signals

-

+

Certain UNIX signals cause the name server to take specific actions, as described in the following table. These signals can be sent using the kill command.

-
- +
@@ -737,11 +640,10 @@ controls { -
-
-
-
-
+
+
+
+
@@ -759,6 +661,6 @@ controls {
-

BIND 9.13.2 (Development Release)

+

BIND 9.13.3-dev (Development Release)

diff --git a/doc/arm/Bv9ARM.ch04.html b/doc/arm/Bv9ARM.ch04.html index 5d77aa762b0647424e40caaedc49502213fd3bf8..7ee3c49404a5f542a2e80af9f40dff845eef73cd 100644 --- a/doc/arm/Bv9ARM.ch04.html +++ b/doc/arm/Bv9ARM.ch04.html @@ -10,7 +10,7 @@ Chapter 4. Advanced DNS Features - + @@ -112,19 +112,17 @@
- -
+

Notify

-

+

DNS NOTIFY is a mechanism that allows master servers to notify their slave servers of changes to a zone's data. In response to a NOTIFY from a master server, the slave will check to see that its version of the zone is the current version and, if not, initiate a zone transfer.

- -

+

For more information about DNS NOTIFY, see the description of the notify option in the section called “Boolean Options” and @@ -132,8 +130,7 @@ the section called “Zone Transfers”. The NOTIFY protocol is specified in RFC 1996.

- -
+

Note

As a slave zone can also be a master to other slaves, named, @@ -143,35 +140,29 @@ zones that it loads.

- -
- -
+
+

Dynamic Update

- -

+

Dynamic Update is a method for adding, replacing or deleting records in a master server by sending it a special form of DNS messages. The format and meaning of these messages is specified in RFC 2136.

- -

+

Dynamic update is enabled by including an allow-update or an update-policy clause in the zone statement.

- -

+

If the zone's update-policy is set to local, updates to the zone will be permitted for the key local-ddns, which will be generated by named at startup. See the section called “Dynamic Update Policies” for more details.

- -

+

Dynamic updates using Kerberos signed requests can be made using the TKEY/GSS protocol by setting either the tkey-gssapi-keytab option, or alternatively @@ -181,20 +172,17 @@ policies for the zone, using the Kerberos principal as the signer for the request.

- -

+

Updating of secure zones (zones using DNSSEC) follows RFC 3007: RRSIG, NSEC and NSEC3 records affected by updates are automatically regenerated by the server using an online zone key. Update authorization is based on transaction signatures and an explicit server policy.

- -
+

The journal file

- -

+

All changes made to a zone using dynamic update are stored in the zone's journal file. This file is automatically created by the server when the first dynamic update takes place. @@ -204,8 +192,7 @@ file unless specifically overridden. The journal file is in a binary format and should not be edited manually.

- -

+

The server will also occasionally write ("dump") the complete contents of the updated zone to its zone file. This is not done immediately after @@ -218,29 +205,25 @@ will be removed when the dump is complete, and can be safely ignored.

- -

+

When a server is restarted after a shutdown or crash, it will replay the journal file to incorporate into the zone any updates that took place after the last zone dump.

- -

+

Changes that result from incoming incremental zone transfers are also journaled in a similar way.

- -

+

The zone files of dynamic zones cannot normally be edited by hand because they are not guaranteed to contain the most recent dynamic changes — those are only in the journal file. The only way to ensure that the zone file of a dynamic zone is up to date is to run rndc stop.

- -

+

If you have to make changes to a dynamic zone manually, the following procedure will work: Disable dynamic updates to the zone using @@ -251,8 +234,7 @@ rndc thaw zone to reload the changed zone and re-enable dynamic updates.

- -

+

rndc sync zone will update the zone file with changes from the journal file without stopping dynamic updates; this may be useful for viewing @@ -260,23 +242,18 @@ file after updating the zone file, use rndc sync -clean.

- -
- -
- -
+
+
+

Incremental Zone Transfers (IXFR)

- -

+

The incremental zone transfer (IXFR) protocol is a way for slave servers to transfer only changed data, instead of having to transfer the entire zone. The IXFR protocol is specified in RFC 1995. See Proposed Standards.

- -

+

When acting as a master, BIND 9 supports IXFR for those zones where the necessary change history information is available. These @@ -287,27 +264,24 @@ ixfr-from-differences is set to yes.

- -

+

When acting as a slave, BIND 9 will attempt to use IXFR unless it is explicitly disabled. For more information about disabling IXFR, see the description of the request-ixfr clause of the server statement.

-
- -
+
+

Split DNS

- -

+

Setting up different views, or visibility, of the DNS space to internal and external resolvers is usually referred to as a Split DNS setup. There are several reasons an organization would want to set up its DNS this way.

-

+

One common reason for setting up a DNS system this way is to hide "internal" DNS information from "external" clients on the Internet. There is some debate as to whether or not this is actually @@ -321,17 +295,17 @@ choose to use a Split DNS to present a consistent view of itself to the outside world.

-

+

Another common reason for setting up a Split DNS system is to allow internal networks that are behind filters or in RFC 1918 space (reserved IP space, as documented in RFC 1918) to resolve DNS on the Internet. Split DNS can also be used to allow mail from outside back in to the internal network.

-
+

Example split DNS setup

-

+

Let's say a company named Example, Inc. (example.com) has several corporate sites that have an internal network with @@ -339,14 +313,14 @@ Internet Protocol (IP) space and an external demilitarized zone (DMZ), or "outside" section of a network, that is available to the public.

-

+

Example, Inc. wants its internal clients to be able to resolve external hostnames and to exchange mail with people on the outside. The company also wants its internal resolvers to have access to certain internal-only zones that are not available at all outside of the internal network.

-

+

In order to accomplish this, the company will set up two sets of name servers. One set will be on the inside network (in the reserved @@ -354,7 +328,7 @@ "proxy" hosts that can talk to both sides of its network, in the DMZ.

-

+

The internal servers will be configured to forward all queries, except queries for site1.internal, site2.internal, site1.example.com, and site2.example.com, to the servers @@ -363,20 +337,20 @@ for site1.example.com, site2.example.com, site1.internal, and site2.internal.

-

+

To protect the site1.internal and site2.internal domains, the internal name servers must be configured to disallow all queries to these domains from any external hosts, including the bastion hosts.

-

+

The external servers, which are on the bastion hosts, will be configured to serve the "public" version of the site1 and site2.example.com zones. This could include things such as the host records for public servers (www.example.com and ftp.example.com), and mail exchange (MX) records (a.mx.example.com and b.mx.example.com).

-

+

In addition, the public site1 and site2.example.com zones should have special MX records that contain wildcard (`*') records pointing to the bastion hosts. This is needed because external mail @@ -385,11 +359,11 @@ be delivered to the bastion host, which can then forward it on to internal hosts.

-

+

Here's an example of a wildcard MX record:

- 
*   IN MX 10 external1.example.com.
-

+

*   IN MX 10 external1.example.com.
+

Now that they accept mail on behalf of anything in the internal network, the bastion hosts will need to know how to deliver mail to internal hosts. In order for this to work properly, the resolvers @@ -397,72 +371,57 @@ the bastion hosts will need to be configured to point to the internal name servers for DNS resolution.

-

+

Queries for internal hostnames will be answered by the internal servers, and queries for external hostnames will be forwarded back out to the DNS servers on the bastion hosts.

-

+

In order for all this to work properly, internal clients will need to be configured to query only the internal name servers for DNS queries. This could also be enforced via selective filtering on the network.

-

+

If everything has been set properly, Example, Inc.'s internal clients will now be able to:

-
    +
    • - Look up any hostnames in the site1 and site2.example.com zones. - -
      • +
    • - Look up any hostnames in the site1.internal and site2.internal domains. - -
      • -
    • - Look up any hostnames on the Internet. -
      • -
    • - Exchange mail with both internal and external people. -
      • + +
    • Look up any hostnames on the Internet.
      • +
    • Exchange mail with both internal and external people.
    -

    +

    Hosts on the Internet will be able to:

    -
      +
      • - Look up any hostnames in the site1 and site2.example.com zones. - -
        • +
      • - Exchange mail with anyone in the site1 and site2.example.com zones. - -
        • +
      - -

      +

      Here is an example configuration for the setup we just described above. Note that this is only configuration information; for information on how to configure your zone files, see the section called “Sample Configurations”.

      - -

      +

      Internal DNS server config:

      - 
       
 acl internals { 172.16.72.0/24; 192.168.1.0/24; };
@@ -524,11 +483,9 @@ zone "site2.internal" {
   allow-transfer { internals; }
 };
      - -

      +

      External (bastion host) DNS server config:

      - 
       acl internals { 172.16.72.0/24; 192.168.1.0/24; };
 
@@ -563,26 +520,22 @@ zone "site2.example.com" {
   allow-transfer { internals; externals; }
 };
      - -

      +

      In the resolv.conf (or equivalent) on the bastion host(s):

      - 
       search ...
 nameserver 172.16.72.2
 nameserver 172.16.72.3
 nameserver 172.16.72.4
      - -
    -
-
+
+
+

TSIG

- -

+

TSIG (Transaction SIGnatures) is a mechanism for authenticating DNS messages, originally specified in RFC 2845. It allows DNS messages to be cryptographically signed using a shared secret. TSIG can @@ -593,12 +546,12 @@ nameserver 172.16.72.4 is critical to the integrity of the server, such as with dynamic UPDATE messages or zone transfers from a master to a slave server.

-

+

This is a guide to setting up TSIG in BIND. It describes the configuration syntax and the process of creating TSIG keys.

-

+

named supports TSIG for server-to-server communication, and some of the tools included with BIND support it for sending messages to @@ -606,32 +559,31 @@ nameserver 172.16.72.4

  • - nsupdate(1) supports TSIG via the +nsupdate(1) supports TSIG via the -k, -l and -y command line options, or via the key command when running interactively.
  • - dig(1) supports TSIG via the +dig(1) supports TSIG via the -k and -y command line options.

- -
+

Generating a Shared Key

-

+

TSIG keys can be generated using the tsig-keygen command; the output of the command is a key directive suitable for inclusion in named.conf. The key name, algorithm and size can be specified by command line parameters; the defaults are "tsig-key", HMAC-SHA256, and 256 bits, respectively.

-

+

Any string which is a valid DNS name can be used as a key name. For example, a key to be shared between servers called host1 and host2 could @@ -640,26 +592,25 @@ nameserver 172.16.72.4 

   $ tsig-keygen host1-host2. > host1-host2.key
-

+

This key may then be copied to both hosts. The key name and secret must be identical on both hosts. (Note: copying a shared secret from one server to another is beyond the scope of the DNS. A secure transport mechanism should be used: secure FTP, SSL, ssh, telephone, encrypted email, etc.)

-

+

tsig-keygen can also be run as ddns-confgen, in which case its output includes additional configuration text for setting up dynamic DNS in named. See ddns-confgen(8) for details.

-
- -
+
+

Loading A New Key

-

+

For a key shared between servers called host1 and host2, the following could be added to each server's @@ -671,11 +622,11 @@ key "host1-host2." { secret "DAopyf1mhCbFVZw7pgmNPBoLUq8wEUT7UuPoLENP2HY="; }; -

+

(This is the same key generated above using tsig-keygen.)

-

+

Since this text contains a secret, it is recommended that either named.conf not be world-readable, or that the key directive @@ -683,27 +634,26 @@ key "host1-host2." { included in named.conf via the include directive.

-

+

Once a key has been added to named.conf and the server has been restarted or reconfigured, the server can recognize the key. If the server receives a message signed by the key, it will be able to verify the signature. If the signature is valid, the response will be signed using the same key.

-

+

TSIG keys that are known to a server can be listed using the command rndc tsig-list.

-
- -
+
+

Instructing the Server to Use a Key

-

+

A server sending a request to another server must be told whether to use a key, and if so, which key to use.

-

+

For example, a key may be specified for each server in the masters statement in the definition of a slave zone; in this case, all SOA QUERY messages, NOTIFY @@ -713,7 +663,7 @@ key "host1-host2." { or slave zone, causing NOTIFY messages to be signed using the specified key.

-

+

Keys can also be specified in a server directive. Adding the following on host1, if the IP address of host2 is 10.1.2.3, would @@ -726,58 +676,56 @@ server 10.1.2.3 { keys { host1-host2. ;}; }; -

+

Multiple keys may be present in the keys statement, but only the first one is used. As this directive does not contain secrets, it can be used in a world-readable file.

-

+

Requests sent by host2 to host1 would not be signed, unless a similar server directive were in host2's configuration file.

-

+

Whenever any server sends a TSIG-signed DNS request, it will expect the response to be signed with the same key. If a response is not signed, or if the signature is not valid, the response will be rejected.

-
- -
+
+

TSIG-Based Access Control

-

+

TSIG keys may be specified in ACL definitions and ACL directives such as allow-query, allow-transfer and allow-update. The above key would be denoted in an ACL element as key host1-host2.

-

+

An example of an allow-update directive using a TSIG key: 

 allow-update { !{ !localnets; any; }; key host1-host2. ;};
-

+

This allows dynamic updates to succeed only if the UPDATE request comes from an address in localnets, and if it is signed using the host1-host2. key.

-

+

See the section called “Dynamic Update Policies” for a discussion of the more flexible update-policy statement.

-
- -
+
+

Errors

-

+

Processing of TSIG-signed messages can result in several errors:

    @@ -803,25 +751,23 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; In all of the above cases, the server will return a response code of NOTAUTH (not authenticated).

    -
-
- -
+
+
+

TKEY

- -

+

TKEY (Transaction KEY) is a mechanism for automatically negotiating a shared secret between two hosts, originally specified in RFC 2930.

-

+

There are several TKEY "modes" that specify how a key is to be generated or assigned. BIND 9 implements only one of these modes: Diffie-Hellman key exchange. Both hosts are required to have a KEY record with algorithm DH (though this record is not required to be present in a zone).

-

+

The TKEY process is initiated by a client or server by sending a query of type TKEY to a TKEY-aware server. The query must include an appropriate KEY record in the additional section, and @@ -833,55 +779,51 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; can then be used by to sign subsequent transactions between the two servers.

-

+

TSIG keys known by the server, including TKEY-negotiated keys, can be listed using rndc tsig-list.

-

+

TKEY-negotiated keys can be deleted from a server using rndc tsig-delete. This can also be done via the TKEY protocol itself, by sending an authenticated TKEY query specifying the "key deletion" mode.

- -
-
+
+

SIG(0)

- -

+

BIND partially supports DNSSEC SIG(0) transaction signatures as specified in RFC 2535 and RFC 2931. SIG(0) uses public/private keys to authenticate messages. Access control is performed in the same manner as TSIG keys; privileges can be granted or denied in ACL directives based on the key name.

-

+

When a SIG(0) signed message is received, it will only be verified if the key is known and trusted by the server. The server will not attempt to recursively fetch or validate the key.

-

+

SIG(0) signing of multiple-message TCP streams is not supported.

-

+

The only tool shipped with BIND 9 that generates SIG(0) signed messages is nsupdate.

-
- -
+
+

DNSSEC

-

+

Cryptographic authentication of DNS information is possible through the DNS Security (DNSSEC-bis) extensions, defined in RFC 4033, RFC 4034, and RFC 4035. This section describes the creation and use of DNSSEC signed zones.

- -

+

In order to set up a DNSSEC secure zone, there are a series of steps which must be followed. BIND 9 ships @@ -894,8 +836,7 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; that the tools shipped with BIND 9.2.x and earlier are not compatible with the current ones.

- -

+

There must also be communication with the administrators of the parent and/or child zone to transmit keys. A zone's security status must be indicated by the parent zone for a DNSSEC capable @@ -904,23 +845,19 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; delegation point.

- -

+

For other servers to trust data in this zone, they must either be statically configured with this zone's zone key or the zone key of another zone above this one in the DNS tree.

- -
+

Generating Keys

- -

+

The dnssec-keygen program is used to generate keys.

- -

+

A secure zone must contain one or more zone keys. The zone keys will sign all other records in the zone, as well as the zone keys of any secure delegated zones. Zone keys must @@ -931,17 +868,14 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; designated as "mandatory to implement" by the IETF; currently the only one is RSASHA1.

- -

+

The following command will generate a 768-bit RSASHA1 key for the child.example zone:

- -

+

dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.

- -

+

Two output files will be produced: Kchild.example.+005+12345.key and Kchild.example.+005+12345.private @@ -957,35 +891,29 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; .key file) is used for signature verification.

- -

+

To generate another key with the same properties (but with a different key tag), repeat the above command.

- -

+

The dnssec-keyfromlabel program is used to get a key pair from a crypto hardware and build the key files. Its usage is similar to dnssec-keygen.

- -

+

The public keys should be inserted into the zone file by including the .key files using $INCLUDE statements.

- -
-
+
+

Signing the Zone

- -

+

The dnssec-signzone program is used to sign a zone.

- -

+

Any keyset files corresponding to secure sub-zones should be present. The zone signer will generate NSEC, NSEC3 @@ -995,19 +923,16 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; is not specified, then DS RRsets for the secure child zones need to be added manually.

- -

+

The following command signs the zone, assuming it is in a file called zone.child.example. By default, all zone keys which have an available private key are used to generate signatures.

- -

+

dnssec-signzone -o child.example zone.child.example

- -

+

One output file is produced: zone.child.example.signed. This file @@ -1015,37 +940,31 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; as the input file for the zone.

- -

dnssec-signzone +

dnssec-signzone will also produce a keyset and dsset files and optionally a dlvset file. These are used to provide the parent zone administrators with the DNSKEYs (or their corresponding DS records) that are the secure entry point to the zone.

- -
- -
+
+

Configuring Servers

- -

+

To enable named to respond appropriately to DNS requests from DNSSEC aware clients, dnssec-enable must be set to yes. This is the default setting.

- -

+

To enable named to validate answers from other servers, the dnssec-enable option must be set to yes, and the dnssec-validation option must be set to either yes or auto.

- -

+

When dnssec-validation is set to auto, a trust anchor for the DNS root zone will automatically be used. This trust anchor is @@ -1065,8 +984,7 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; built with configure --disable-auto-validation, in which case the default is yes.

- -

+

trusted-keys are copies of DNSKEY RRs for zones that are used to form the first link in the cryptographic chain of trust. All keys listed in @@ -1074,27 +992,23 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; are deemed to exist and only the listed keys will be used to validated the DNSKEY RRset that they are from.

- -

+

managed-keys are trusted keys which are automatically kept up to date via RFC 5011 trust anchor maintenance.

- -

+

trusted-keys and managed-keys are described in more detail later in this document.

- -

+

Unlike BIND 8, BIND 9 does not verify signatures on load, so zone keys for authoritative zones do not need to be specified in the configuration file.

- -

+

After DNSSEC gets established, a typical DNSSEC configuration will look something like the following. It has one or more public keys for the root. This allows answers from @@ -1104,7 +1018,6 @@ allow-update { !{ !localnets; any; }; key host1-host2. ;}; is immune to compromises in the DNSSEC components of the security of parent zones.

- 
 managed-keys {
         /* Root Key */
@@ -1157,65 +1070,56 @@ options {
         dnssec-validation yes;
 };
- -
+

Note

None of the keys listed in this example are valid. In particular, the root key is not valid.

- -

+

When DNSSEC validation is enabled and properly configured, the resolver will reject any answers from signed, secure zones which fail to validate, and will return SERVFAIL to the client.

- -

+

Responses may fail to validate for any of several reasons, including missing, expired, or invalid signatures, a key which does not match the DS RRset in the parent zone, or an insecure response from a zone which, according to its parent, should have been secure.

- -
+

Note

-

+

When the validator receives a response from an unsigned zone that has a signed parent, it must confirm with the parent that the zone was intentionally left unsigned. It does this by verifying, via signed and validated NSEC/NSEC3 records, that the parent zone contains no DS records for the child.

-

+

If the validator can prove that the zone is insecure, then the response is accepted. However, if it cannot, then it must assume an insecure response to be a forgery; it rejects the response and logs an error.

-

+

The logged error reads "insecurity proof failed" and "got insecure response; parent indicates it should be secure".

-
-
-
- -
+
+
+
+

DNSSEC, Dynamic Zones, and Automatic Signing

- -
-

-Converting from insecure to secure

- -
-

Changing a zone from insecure to secure can be done in two +

+Converting from insecure to secure

+

Changing a zone from insecure to secure can be done in two ways: using a dynamic DNS update, or the auto-dnssec zone option.

-

For either method, you need to configure +

For either method, you need to configure named so that it can see the K* files which contain the public and private parts of the keys that will be used to sign the zone. These files @@ -1223,7 +1127,7 @@ options { dnssec-keygen. You can do this by placing them in the key-directory, as specified in named.conf:

- 
+
 	zone example.net {
 		type master;
 		update-policy local;
@@ -1231,35 +1135,32 @@ options {
 		key-directory "dynamic/example.net";
 	};
 

-  
If one KSK and one ZSK DNSKEY key have been generated, this
+
If one KSK and one ZSK DNSKEY key have been generated, this
   configuration will cause all records in the zone to be signed
   with the ZSK, and the DNSKEY RRset to be signed with the KSK as
   well. An NSEC chain will be generated as part of the initial
   signing process.

-  

-

-Dynamic DNS update method

-
-  

-  
To insert the keys via dynamic update:

-  
+

+Dynamic DNS update method

+
To insert the keys via dynamic update:

+
 	% nsupdate
 	> ttl 3600
 	> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
 	> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
 	> send
 

-  
While the update request will complete almost immediately,
+
While the update request will complete almost immediately,
   the zone will not be completely signed until
   named has had time to walk the zone and
   generate the NSEC and RRSIG records. The NSEC record at the apex
   will be added last, to signal that there is a complete NSEC
   chain.

-  
If you wish to sign using NSEC3 instead of NSEC, you should
+
If you wish to sign using NSEC3 instead of NSEC, you should
   add an NSEC3PARAM record to the initial update request. If you
   wish the NSEC3 chain to have the OPTOUT bit set, set it in the
   flags field of the NSEC3PARAM record.

-  
+
 	% nsupdate
 	> ttl 3600
 	> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
@@ -1267,32 +1168,29 @@ options {
 	> update add example.net NSEC3PARAM 1 1 100 1234567890
 	> send
 

-  
Again, this update request will complete almost
+
Again, this update request will complete almost
   immediately; however, the record won't show up until
   named has had a chance to build/remove the
   relevant chain. A private type record will be created to record
   the state of the operation (see below for more details), and will
   be removed once the operation completes.

-  
While the initial signing and NSEC/NSEC3 chain generation
+
While the initial signing and NSEC/NSEC3 chain generation
   is happening, other updates are possible as well.

-  

-

-Fully automatic zone signing

-
-  

-  
To enable automatic signing, add the
+

+Fully automatic zone signing

+
To enable automatic signing, add the
   auto-dnssec option to the zone statement in
   named.conf.
   auto-dnssec has two possible arguments:
   allow or
   maintain.

-  
With
+
With
   auto-dnssec allow,
   named can search the key directory for keys
   matching the zone, insert them into the zone, and use them to
   sign the zone. It will do so only when it receives an
   rndc sign <zonename>.

-  

+

   
   auto-dnssec maintain includes the above
   functionality, but will also automatically adjust the zone's
@@ -1300,7 +1198,7 @@ options {
   (See dnssec-keygen(8) and
   dnssec-settime(8) for more information.)
   

-  

+

   named will periodically search the key directory
   for keys matching the zone, and if the keys' metadata indicates
   that any change should be made the zone, such as adding, removing,
@@ -1310,21 +1208,21 @@ options {
   to a maximum of 24 hours.  The rndc loadkeys forces
   named to check for key updates immediately.
   

-  

+

   If keys are present in the key directory the first time the zone
   is loaded, the zone will be signed immediately, without waiting for an
   rndc sign or rndc loadkeys
   command. (Those commands can still be used when there are unscheduled
   key changes, however.)
   

-  

+

   When new keys are added to a zone, the TTL is set to match that
   of any existing DNSKEY RRset. If there is no existing DNSKEY RRset,
   then the TTL will be set to the TTL specified when the key was
   created (using the dnssec-keygen -L option), if
   any, or to the SOA TTL.
   

-  

+

   If you wish the zone to be signed using NSEC3 instead of NSEC,
   submit an NSEC3PARAM record via dynamic update prior to the
   scheduled publication and activation of the keys.  If you wish the
@@ -1334,28 +1232,25 @@ options {
   the zone is signed and the NSEC3 chain is completed, the NSEC3PARAM
   record will appear in the zone.
   

-  
Using the
+
Using the
   auto-dnssec option requires the zone to be
   configured to allow dynamic updates, by adding an
   allow-update or
   update-policy statement to the zone
   configuration. If this has not been done, the configuration will
   fail.

-  

-

-Private-type records

-
-  

-  
The state of the signing process is signaled by
+

+Private-type records

+
The state of the signing process is signaled by
   private-type records (with a default type value of 65534). When
   signing is complete, these records will have a nonzero value for
   the final octet (for those records which have a nonzero initial
   octet).

-  
The private type record format: If the first octet is
+
The private type record format: If the first octet is
   non-zero then the record indicates that the zone needs to be
   signed with the key matching the record, or that all signatures
   that match the record should be removed.

-  

+

     

 


 

@@ -1366,15 +1261,15 @@ options {
 

 

   

-  
Only records flagged as "complete" can be removed via
+
Only records flagged as "complete" can be removed via
   dynamic update. Attempts to remove other private type records
   will be silently ignored.

-  
If the first octet is zero (this is a reserved algorithm
+
If the first octet is zero (this is a reserved algorithm
   number that should never appear in a DNSKEY record) then the
   record indicates changes to the NSEC3 chains are in progress. The
   rest of the record contains an NSEC3PARAM record. The flag field
   tells what operation to perform based on the flag bits.

-  

+

     

 


 

@@ -1385,20 +1280,14 @@ options {
 

 

   

-  

-

-DNSKEY rollovers

-
-  

-  
As with insecure-to-secure conversions, rolling DNSSEC
+

+DNSKEY rollovers

+
As with insecure-to-secure conversions, rolling DNSSEC
   keys can be done in two ways: using a dynamic DNS update, or the
   auto-dnssec zone option.

-  

-

-Dynamic DNS update method

-
-  

-  
 To perform key rollovers via dynamic update, you need to add
+

+Dynamic DNS update method

+
 To perform key rollovers via dynamic update, you need to add
   the K* files for the new keys so that
   named can find them. You can then add the new
   DNSKEY RRs via dynamic update.
@@ -1406,24 +1295,21 @@ options {
   with the new keys. When the signing is complete the private type
   records will be updated so that the last octet is non
   zero.

-  
If this is for a KSK you need to inform the parent and any
+
If this is for a KSK you need to inform the parent and any
   trust anchor repositories of the new KSK.

-  
You should then wait for the maximum TTL in the zone before
+
You should then wait for the maximum TTL in the zone before
   removing the old DNSKEY. If it is a KSK that is being updated,
   you also need to wait for the DS RRset in the parent to be
   updated and its TTL to expire. This ensures that all clients will
   be able to verify at least one signature when you remove the old
   DNSKEY.

-  
The old DNSKEY can be removed via UPDATE. Take care to
+
The old DNSKEY can be removed via UPDATE. Take care to
   specify the correct key.
   named will clean out any signatures generated
   by the old key after the update completes.

-  

-

-Automatic key rollovers

-
-  

-  
When a new key reaches its activation date (as set by
+

+Automatic key rollovers

+
When a new key reaches its activation date (as set by
   dnssec-keygen or dnssec-settime),
   if the auto-dnssec zone option is set to
   maintain, named will
@@ -1436,69 +1322,51 @@ options {
   signature validity periods expire.  By default, this rollover
   completes in 30 days, after which it will be safe to remove the
   old key from the DNSKEY RRset.

-  

-

-NSEC3PARAM rollovers via UPDATE

-
-  

-  
Add the new NSEC3PARAM record via dynamic update. When the
+

+NSEC3PARAM rollovers via UPDATE

+
Add the new NSEC3PARAM record via dynamic update. When the
   new NSEC3 chain has been generated, the NSEC3PARAM flag field
   will be zero. At this point you can remove the old NSEC3PARAM
   record. The old chain will be removed after the update request
   completes.

-  

-

-Converting from NSEC to NSEC3

-
-  

-  
To do this, you just need to add an NSEC3PARAM record. When
+

+Converting from NSEC to NSEC3

+
To do this, you just need to add an NSEC3PARAM record. When
   the conversion is complete, the NSEC chain will have been removed
   and the NSEC3PARAM record will have a zero flag field. The NSEC3
   chain will be generated before the NSEC chain is
   destroyed.

-  

-

-Converting from NSEC3 to NSEC

-
-  

-  
To do this, use nsupdate to
+

+Converting from NSEC3 to NSEC

+
To do this, use nsupdate to
   remove all NSEC3PARAM records with a zero flag
   field. The NSEC chain will be generated before the NSEC3 chain is
   removed.

-  

-

-Converting from secure to insecure

-
-  

-  
To convert a signed zone to unsigned using dynamic DNS,
+

+Converting from secure to insecure

+
To convert a signed zone to unsigned using dynamic DNS,
   delete all the DNSKEY records from the zone apex using
   nsupdate. All signatures, NSEC or NSEC3 chains,
   and associated NSEC3PARAM records will be removed automatically.
   This will take place after the update request completes.

-  
 This requires the
+
 This requires the
   dnssec-secure-to-insecure option to be set to
   yes in
   named.conf.

-  
In addition, if the auto-dnssec maintain
+
In addition, if the auto-dnssec maintain
   zone statement is used, it should be removed or changed to
   allow instead (or it will re-sign).
   

-  

-

-Periodic re-signing

-
-  

-  
In any secure zone which supports dynamic updates, named
+

+Periodic re-signing

+
In any secure zone which supports dynamic updates, named
   will periodically re-sign RRsets which have not been re-signed as
   a result of some update action. The signature lifetimes will be
   adjusted so as to spread the re-sign load over time rather than
   all at once.

-  

-

-NSEC3 and OPTOUT

-
-  

-  

+

+NSEC3 and OPTOUT

+

   named only supports creating new NSEC3 chains
   where all the NSEC3 records in the zone have the same OPTOUT
   state.
@@ -1509,41 +1377,34 @@ options {
   changed if the OPTOUT state of an individual NSEC3 needs to be
   changed.
- -
+

Dynamic Trust Anchor Management

- -

+

BIND is able to maintain DNSSEC trust anchors using RFC 5011 key management. This feature allows named to keep track of changes to critical DNSSEC keys without any need for the operator to make changes to configuration files.

- -
+

Validating Resolver

- - -

To configure a validating resolver to use RFC 5011 to +

To configure a validating resolver to use RFC 5011 to maintain a trust anchor, configure the trust anchor using a managed-keys statement. Information about this can be found in the section called “managed-keys Statement Definition and Usage”.

- -
-
+
+

Authoritative Server

- -

To set up an authoritative zone for RFC 5011 trust anchor +

To set up an authoritative zone for RFC 5011 trust anchor maintenance, generate two (or more) key signing keys (KSKs) for the zone. Sign the zone with one of them; this is the "active" KSK. All KSKs which do not sign the zone are "stand-by" keys.

-

Any validating resolver which is configured to use the +

Any validating resolver which is configured to use the active KSK as an RFC 5011-managed trust anchor will take note of the stand-by KSKs in the zone's DNSKEY RRset, and store them for future reference. The resolver will recheck the zone @@ -1552,7 +1413,7 @@ options { anchor for the zone. Any time after this 30-day acceptance timer has completed, the active KSK can be revoked, and the zone can be "rolled over" to the newly accepted key.

-

The easiest way to place a stand-by key in a zone is to +

The easiest way to place a stand-by key in a zone is to use the "smart signing" features of dnssec-keygen and dnssec-signzone. If a key with a publication @@ -1560,56 +1421,54 @@ options { the future, " dnssec-signzone -S" will include the DNSKEY record in the zone, but will not sign with it:

- 
+
 $ dnssec-keygen -K keys -f KSK -P now -A now+2y example.net
 $ dnssec-signzone -S -K keys example.net
 

-    
To revoke a key, the new command
+
To revoke a key, the new command
     dnssec-revoke has been added. This adds the
     REVOKED bit to the key flags and re-generates the
     K*.key and
     K*.private files.

-    
After revoking the active key, the zone must be signed
+
After revoking the active key, the zone must be signed
     with both the revoked KSK and the new active KSK. (Smart
     signing takes care of this automatically.)

-    
Once a key has been revoked and used to sign the DNSKEY
+
Once a key has been revoked and used to sign the DNSKEY
     RRset in which it appears, that key will never again be
     accepted as a valid trust anchor by the resolver. However,
     validation can proceed using the new active key (which had been
     accepted by the resolver when it was a stand-by key).

-    
See RFC 5011 for more details on key rollover
+
See RFC 5011 for more details on key rollover
     scenarios.

-    
When a key has been revoked, its key ID changes,
+
When a key has been revoked, its key ID changes,
     increasing by 128, and wrapping around at 65535. So, for
     example, the key "Kexample.com.+005+10000" becomes
     "Kexample.com.+005+10128".

-    
If two keys have IDs exactly 128 apart, and one is
+
If two keys have IDs exactly 128 apart, and one is
     revoked, then the two key IDs will collide, causing several
     problems. To prevent this,
     dnssec-keygen will not generate a new key if
     another key is present which may collide. This checking will
     only occur if the new keys are written to the same directory
     which holds all other keys in use for that zone.

-    
Older versions of BIND 9 did not have this precaution.
+
Older versions of BIND 9 did not have this precaution.
     Exercise caution if using key revocation on keys that were
     generated by previous releases, or if using keys stored in
     multiple directories or on multiple machines.

-    
It is expected that a future release of BIND 9 will
+
It is expected that a future release of BIND 9 will
     address this problem in a different way, by storing revoked
     keys with their original unrevoked key IDs.

-
- -
+
+

PKCS#11 (Cryptoki) support

- -

+

PKCS#11 (Public Key Cryptography Standard #11) defines a platform-independent API for the control of hardware security modules (HSMs) and other cryptographic support devices.

-

+

BIND 9 is known to work with three HSMs: The AEP Keyper, which has been tested with Debian Linux, Solaris x86 and Windows Server 2003; the Thales nShield, tested with Debian Linux; and the Sun SCA 6000 @@ -1618,13 +1477,13 @@ $ dnssec-signzone -S -K keys example.net< a software-based HSM simulator library produced by the OpenDNSSEC project.

-

+

PKCS#11 makes use of a "provider library": a dynamically loadable library which provides a low-level PKCS#11 interface to drive the HSM hardware. The PKCS#11 provider library comes from the HSM vendor, and it is specific to the HSM to be controlled.

-

+

There are two available mechanisms for PKCS#11 support in BIND 9: OpenSSL-based PKCS#11 and native PKCS#11. When using the first mechanism, BIND uses a modified version of OpenSSL, which loads @@ -1634,21 +1493,19 @@ $ dnssec-signzone -S -K keys example.net< OpenSSL completely; BIND loads the provider library itself, and uses the PKCS#11 API to drive the HSM directly.

-
+

Prerequisites

- -

+

See the documentation provided by your HSM vendor for information about installing, initializing, testing and troubleshooting the HSM.

-
-
+
+

Native PKCS#11

- -

+

Native PKCS#11 mode will only work with an HSM capable of carrying out every cryptographic operation BIND 9 may need. The HSM's provider library must have a complete implementation @@ -1660,15 +1517,15 @@ $ dnssec-signzone -S -K keys example.net< native PKCS#11, it is expected that OpenSSL-based PKCS#11 will be deprecated.)

-

+

To build BIND with native PKCS#11, configure as follows:

- 
+
 $ cd bind9
 $ ./configure --enable-native-pkcs11 \
     --with-pkcs11=provider-library-path
     

-    

+

       This will cause all BIND tools, including named
       and the dnssec-* and pkcs11-*
       tools, to use the PKCS#11 provider library specified in
@@ -1678,11 +1535,10 @@ $ ./configure --enable-native-pkcs11 \
       dnssec-* tools, or the -m in
       the pkcs11-* tools.)
     

-    

+

 

 Building SoftHSMv2

-
-      

+

 	SoftHSMv2, the latest development version of SoftHSM, is available
 	from
 	
@@ -1700,7 +1556,7 @@ $ ./configure --enable-native-pkcs11 \
 	cryptographic functions, but when using it for native PKCS#11 in
 	BIND, OpenSSL is required.
       

-      

+

 	By default, the SoftHSMv2 configuration file is
 	prefix/etc/softhsm2.conf (where
 	prefix is configured at compile time).
@@ -1708,20 +1564,19 @@ $ ./configure --enable-native-pkcs11 \
 	variable.  The SoftHSMv2 cryptographic store must be installed and
 	initialized before using it with BIND.
       

-      
+
 $  cd SoftHSMv2 
 $  configure --with-crypto-backend=openssl --prefix=/opt/pkcs11/usr 
 $  make 
 $  make install 
 $  /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label softhsmv2 
       

-    

-  

-  

+

+
+

OpenSSL-based PKCS#11

- -

+

OpenSSL-based PKCS#11 mode uses a modified version of the OpenSSL library; stock OpenSSL does not fully support PKCS#11. ISC provides a patch to OpenSSL to correct this. This patch is @@ -1729,23 +1584,20 @@ $ /opt/pkcs11/usr/bin/softhsm-util --init-token modified by ISC to provide new features such as PIN management and key-by-reference.

-

+

There are two "flavors" of PKCS#11 support provided by the patched OpenSSL, one of which must be chosen at configuration time. The correct choice depends on the HSM hardware:

-
    -
  • -

    +

      +

    • Use 'crypto-accelerator' with HSMs that have hardware cryptographic acceleration features, such as the SCA 6000 board. This causes OpenSSL to run all supported cryptographic operations in the HSM. -

      -
      • -
    • -

      +

      • +

    • Use 'sign-only' with HSMs that are designed to function primarily as secure key storage devices, but lack hardware acceleration. These devices are highly secure, but @@ -1756,10 +1608,9 @@ $ /opt/pkcs11/usr/bin/softhsm-util --init-token such as zone signing, and to use the system CPU for all other computationally-intensive operations. The AEP Keyper is an example of such a device. -

      -
      • +

    -

    +

    The modified OpenSSL code is included in the BIND 9 release, in the form of a context diff against the latest versions of OpenSSL. OpenSSL 0.9.8, 1.0.0, 1.0.1 and 1.0.2 are supported; @@ -1767,7 +1618,7 @@ $ /opt/pkcs11/usr/bin/softhsm-util --init-token follow, we use OpenSSL 0.9.8, but the same methods work with OpenSSL 1.0.0 through 1.0.2.

    -
    +

    Note

    The OpenSSL patches as of this writing (January 2016) @@ -1777,28 +1628,27 @@ $ /opt/pkcs11/usr/bin/softhsm-util --init-token is expected to change.

    -

    +

    Before building BIND 9 with PKCS#11 support, it will be necessary to build OpenSSL with the patch in place, and configure it with the path to your HSM's PKCS#11 provider library.

    -
    +

    Patching OpenSSL

    - - 
    +
     $ wget http://www.openssl.org/source/openssl-0.9.8zc.tar.gz
   
    
-      
    Extract the tarball:
    
-      
    +
    Extract the tarball:
    
+
     $ tar zxf openssl-0.9.8zc.tar.gz
 
    
-      
    Apply the patch from the BIND 9 release:
    
-      
    +
    Apply the patch from the BIND 9 release:
    
+
     $ patch -p1 -d openssl-0.9.8zc \
 	      < bind9/bin/pkcs11/openssl-0.9.8zc-patch
 
    
-      
    
+
    
 
    Note
    
 
    
 	The patch file may not be compatible with the
@@ -1806,93 +1656,77 @@ $ patch -p1 -d openssl-0.9.8zc \
 	install GNU patch.
       
    
 
    
-      
    
+
    
 	When building OpenSSL, place it in a non-standard
 	location so that it does not interfere with OpenSSL libraries
 	elsewhere on the system. In the following examples, we choose
 	to install into "/opt/pkcs11/usr". We will use this location
 	when we configure BIND 9.
       
    
-      
    
+
    
 	Later, when building BIND 9, the location of the custom-built
 	OpenSSL library will need to be specified via configure.
       
    
-    
    
-    
    
+
    
+
    
 
    
 Building OpenSSL for the AEP Keyper on Linux
    
-      
-
-      
    
+
    
 	The AEP Keyper is a highly secure key storage device,
 	but does not provide hardware cryptographic acceleration. It
 	can carry out cryptographic operations, but it is probably
 	slower than your system's CPU. Therefore, we choose the
 	'sign-only' flavor when building OpenSSL.
       
    
-      
    
+
    
 	The Keyper-specific PKCS#11 provider library is
 	delivered with the Keyper software. In this example, we place
 	it /opt/pkcs11/usr/lib:
       
    
-      
    +
     $ cp pkcs11.GCC4.0.2.so.4.05 /opt/pkcs11/usr/lib/libpkcs11.so
 
    
-      
    
-	The Keyper library requires threads, so we
-	must specify -pthread.
-      
    
-      
    +
     $ cd openssl-0.9.8zc
-$ ./Configure linux-x86_64 -pthread \
+$ ./Configure linux-x86_64 \
 	    --pk11-libname=/opt/pkcs11/usr/lib/libpkcs11.so \
 	    --pk11-flavor=sign-only \
 	    --prefix=/opt/pkcs11/usr
 
    
-      
    
-	After configuring, run "make"
-	and "make test". If "make
-	test" fails with "pthread_atfork() not found", you forgot to
-	add the -pthread above.
-      
    
-    
    
-    
    
+
    
+
    
 
    
 Building OpenSSL for the SCA 6000 on Solaris
    
-      
-
-      
    
+
    
 	The SCA-6000 PKCS#11 provider is installed as a system
 	library, libpkcs11. It is a true crypto accelerator, up to 4
 	times faster than any CPU, so the flavor shall be
 	'crypto-accelerator'.
       
    
-      
    
+
    
 	In this example, we are building on Solaris x86 on an
 	AMD64 system.
       
    
-      
    +
     $ cd openssl-0.9.8zc
 $ ./Configure solaris64-x86_64-cc \
 	    --pk11-libname=/usr/lib/64/libpkcs11.so \
 	    --pk11-flavor=crypto-accelerator \
 	    --prefix=/opt/pkcs11/usr
 
    
-      
    
+
    
 	(For a 32-bit build, use "solaris-x86-cc" and /usr/lib/libpkcs11.so.)
       
    
-      
    
+
    
 	After configuring, run
 	make and
 	make test.
       
    
-    
    
-    
    
+
    
+
    
 
    
 Building OpenSSL for SoftHSM
    
-      
-
-      
    
+
    
 	SoftHSM (version 1) is a software library developed by the
 	OpenDNSSEC project
 	(
@@ -1905,13 +1739,13 @@ $ ./Configure solaris64-x86_64-cc \
 	less secure than a true HSM, it can allow you to experiment
 	with PKCS#11 when an HSM is not available.
       
    
-      
    
+
    
 	The SoftHSM cryptographic store must be installed and
 	initialized before using it with OpenSSL, and the SOFTHSM_CONF
 	environment variable must always point to the SoftHSM configuration
 	file:
       
    
-      
    +
     $  cd softhsm-1.3.7 
 $  configure --prefix=/opt/pkcs11/usr 
 $  make 
@@ -1920,118 +1754,103 @@ $  export SOFTHSM_CONF=/opt/pkcs11/softhsm.conf
 $  echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF 
 $  /opt/pkcs11/usr/bin/softhsm --init-token 0 --slot 0 --label softhsm 
 
    
-      
    
+
    
 	SoftHSM can perform all cryptographic operations, but
 	since it only uses your system CPU, there is no advantage to using
 	it for anything but signing.  Therefore, we choose the 'sign-only'
 	flavor when building OpenSSL.
       
    
-      
    +
     $ cd openssl-0.9.8zc
-$ ./Configure linux-x86_64 -pthread \
+$ ./Configure linux-x86_64 \
 	    --pk11-libname=/opt/pkcs11/usr/lib/libsofthsm.so \
 	    --pk11-flavor=sign-only \
 	    --prefix=/opt/pkcs11/usr
 
    
-      
    
+
    
 	After configuring, run "make"
 	and "make test".
       
    
-    
    
-    
    
+
    +

    Once you have built OpenSSL, run "apps/openssl engine pkcs11" to confirm that PKCS#11 support was compiled in correctly. The output should be one of the following lines, depending on the flavor selected:

    - 
    +
     	(pkcs11) PKCS #11 engine support (sign only)
 
    
-    
    Or:
    
-    
    +
    Or:
    
+
     	(pkcs11) PKCS #11 engine support (crypto accelerator)
 
    
-    
    
+
    
       Next, run
       "apps/openssl engine pkcs11 -t". This will
       attempt to initialize the PKCS#11 engine. If it is able to
       do so successfully, it will report
       “[ available ]”.
     
    
-    
    
+
    
       If the output is correct, run
       "make install" which will install the
       modified OpenSSL suite to /opt/pkcs11/usr.
     
    
-    
    
+
    
 
    
-      
-
-      
    
-	To link with the PKCS#11 provider, threads must be
-	enabled in the BIND 9 build.
-      
    
-      
    +
     $ cd ../bind9
-$ ./configure --enable-threads \
+$ ./configure \
 	   --with-openssl=/opt/pkcs11/usr \
 	   --with-pkcs11=/opt/pkcs11/usr/lib/libpkcs11.so
 
    
-    
    
-    
    
+
    
+
    
 
    
 Configuring BIND 9 for Solaris with the SCA 6000
    
-      
-
-      
    
-	To link with the PKCS#11 provider, threads must be
-	enabled in the BIND 9 build.
-      
    
-      
    +
     $ cd ../bind9
-$ ./configure CC="cc -xarch=amd64" --enable-threads \
+$ ./configure CC="cc -xarch=amd64" \
 	    --with-openssl=/opt/pkcs11/usr \
 	    --with-pkcs11=/usr/lib/64/libpkcs11.so
 
    
-      
    (For a 32-bit build, omit CC="cc -xarch=amd64".)
    
-      
    
+
    (For a 32-bit build, omit CC="cc -xarch=amd64".)
    
+
    
 	If configure complains about OpenSSL not working, you
 	may have a 32/64-bit architecture mismatch. Or, you may have
 	incorrectly specified the path to OpenSSL (it should be the
 	same as the --prefix argument to the OpenSSL
 	Configure).
       
    
-    
    
-    
    
+
    
+
    
 
    
 Configuring BIND 9 for SoftHSM
    
-      
-
-      
    +
     $ cd ../bind9
-$ ./configure --enable-threads \
+$ ./configure \
 	   --with-openssl=/opt/pkcs11/usr \
 	   --with-pkcs11=/opt/pkcs11/usr/lib/libsofthsm.so
 
    
-    
    
-    
    
+
    
+
    
       After configuring, run
       "make",
       "make test" and
       "make install".
     
    
-    
    
+
    
       (Note: If "make test" fails in the "pkcs11" system test, you may
       have forgotten to set the SOFTHSM_CONF environment variable.)
     
    
-
    -
    +
    +

    PKCS#11 Tools

    - -

    +

    BIND 9 includes a minimal set of tools to operate the HSM, including pkcs11-keygen to generate a new key pair @@ -2041,7 +1860,7 @@ $ ./configure --enable-threads \ pkcs11-destroy to remove objects, and pkcs11-tokens to list available tokens.

    -

    +

    In UNIX/Linux builds, these tools are built only if BIND 9 is configured with the --with-pkcs11 option. (Note: If --with-pkcs11 is set to "yes", rather than to the path of the @@ -2050,25 +1869,24 @@ $ ./configure --enable-threads \ PKCS11_PROVIDER environment variable to specify the path to the provider.)

    -
    -
    +
    +

    Using the HSM

    - -

    +

    For OpenSSL-based PKCS#11, we must first set up the runtime environment so the OpenSSL and PKCS#11 libraries can be loaded:

    - 
    +
     $ export LD_LIBRARY_PATH=/opt/pkcs11/usr/lib:${LD_LIBRARY_PATH}
 
    
-    
    
+
    
       This causes named and other binaries to load
       the OpenSSL library from /opt/pkcs11/usr/lib
       rather than from the default location.  This step is not necessary
       when using native PKCS#11.
     
    
-    
    
+
    
       Some HSMs require other environment variables to be set.
       For example, when operating an AEP Keyper, it is necessary to
       specify the location of the "machine" file, which stores
@@ -2077,10 +1895,10 @@ $ export LD_LIBRARY_PATH=/opt/pkcs11/usr/lib:${L
       /opt/Keyper/PKCS11Provider/machine,
       use:
     
    
-    
    +
     $ export KEYPER_LIBRARY_PATH=/opt/Keyper/PKCS11Provider
 
    
-    
    
+
    
       Such environment variables must be set whenever running
       any tool that uses the HSM, including
       pkcs11-keygen,
@@ -2091,31 +1909,31 @@ $ export KEYPER_LIBRARY_PATH=/opt/Keyper/PKCS11P
       dnssec-keygen, and
       named.
     
    
-    
    
+
    
       We can now create and use keys in the HSM. In this case,
       we will create a 2048 bit key and give it the label
       "sample-ksk":
     
    
-    
    +
     $ pkcs11-keygen -b 2048 -l sample-ksk
 
    
-    
    To confirm that the key exists:
    
-    
    +
    To confirm that the key exists:
    
+
     $ pkcs11-list
 Enter PIN:
 object[0]: handle 2147483658 class 3 label[8] 'sample-ksk' id[0]
 object[1]: handle 2147483657 class 2 label[8] 'sample-ksk' id[0]
 
    
-    
    
+
    
       Before using this key to sign a zone, we must create a
       pair of BIND 9 key files. The "dnssec-keyfromlabel" utility
       does this. In this case, we will be using the HSM key
       "sample-ksk" as the key-signing key for "example.net":
     
    
-    
    +
     $ dnssec-keyfromlabel -l sample-ksk -f KSK example.net
 
    
-    
    
+
    
       The resulting K*.key and K*.private files can now be used
       to sign the zone. Unlike normal K* files, which contain both
       public and private key data, these files will contain only the
@@ -2123,31 +1941,31 @@ $ dnssec-keyfromlabel -l sample-ksk -f KSK examp
       remains stored within the HSM. Signing with the private key takes
       place inside the HSM.
     
    
-    
    
+
    
       If you wish to generate a second key in the HSM for use
       as a zone-signing key, follow the same procedure above, using a
       different keylabel, a smaller key size, and omitting "-f KSK"
       from the dnssec-keyfromlabel arguments:
     
    
-    
    
+
    
       (Note: When using OpenSSL-based PKCS#11 the label is an arbitrary
       string which identifies the key.  With native PKCS#11, the label is
       a PKCS#11 URI string which may include other details about the key
       and the HSM, including its PIN. See
       dnssec-keyfromlabel(8) for details.)
     
    
-    
    +
     $ pkcs11-keygen -b 1024 -l sample-zsk
 $ dnssec-keyfromlabel -l sample-zsk example.net
 
    
-    
    
+
    
       Alternatively, you may prefer to generate a conventional
       on-disk key, using dnssec-keygen:
     
    
-    
    +
     $ dnssec-keygen example.net
 
    
-    
    
+
    
       This provides less security than an HSM key, but since
       HSMs can be slow or cumbersome to use for security reasons, it
       may be more efficient to reserve HSM keys for use in the less
@@ -2157,13 +1975,13 @@ $ dnssec-keygen example.net
       there is no speed advantage to using on-disk keys, as cryptographic
       operations will be done by the HSM regardless.)
     
    
-    
    
+
    
       Now you can sign the zone. (Note: If not using the -S
       option to dnssec-signzone, it will be
       necessary to add the contents of both K*.key
       files to the zone master file before signing it.)
     
    
-    
    +
     $ dnssec-signzone -S example.net
 Enter PIN:
 Verifying the zone using the following algorithms:
@@ -2172,12 +1990,11 @@ Zone signing complete:
 Algorithm: NSEC3RSASHA1: ZSKs: 1, KSKs: 1 active, 0 revoked, 0 stand-by
 example.net.signed
 
    
-
    -
    +
    +

    Specifying the engine on the command line

    - -

    +

    When using OpenSSL-based PKCS#11, the "engine" to be used by OpenSSL can be specified in named and all of the BIND dnssec-* tools by using the "-E @@ -2187,30 +2004,29 @@ example.net.signed for some reason you wish to use a different OpenSSL engine.

    -

    +

    If you wish to disable use of the "pkcs11" engine — for troubleshooting purposes, or because the HSM is unavailable — set the engine to the empty string. For example:

    - 
    +
     $ dnssec-signzone -E '' -S example.net
 
    
-    
    
+
    
       This causes
       dnssec-signzone to run as if it were compiled
       without the --with-pkcs11 option.
     
    
-    
    
+
    
       When built with native PKCS#11 mode, the "engine" option has a
       different meaning: it specifies the path to the PKCS#11 provider
       library.  This may be useful when testing a new provider library.
     
    
-
    -
    +
    +

    Running named with automatic zone re-signing

    - -

    +

    If you want named to dynamically re-sign zones using HSM keys, and/or to to sign new records inserted via nsupdate, then named must have access to the HSM PIN. In OpenSSL-based PKCS#11, @@ -2218,13 +2034,13 @@ $ dnssec-signzone -E '' -S example.net/opt/pkcs11/usr/ssl/openssl.cnf).

    -

    +

    The location of the openssl.cnf file can be overridden by setting the OPENSSL_CONF environment variable before running named.

    -

    Sample openssl.cnf:

    - 
    +
    Sample openssl.cnf:
    
+
     	openssl_conf = openssl_def
 	[ openssl_def ]
 	engines = engine_section
@@ -2233,42 +2049,40 @@ $ dnssec-signzone -E '' -S example.net<PLACE PIN HERE>
 
    
-    
    
+
    
       This will also allow the dnssec-* tools to access the HSM
       without PIN entry. (The pkcs11-* tools access the HSM directly,
       not via OpenSSL, so a PIN will still be required to use
       them.)
     
    
-    
    
+
    
       In native PKCS#11 mode, the PIN can be provided in a file specified
       as an attribute of the key's label.  For example, if a key had the label
       pkcs11:object=local-zsk;pin-source=/etc/hsmpin,
       then the PIN would be read from the file
       /etc/hsmpin.
     
    
-    
    
+
    
 
    Warning
    
-      
    
+
    
 	Placing the HSM's PIN in a text file in this manner may reduce the
 	security advantage of using an HSM. Be sure this is what you want to
 	do before configuring the system in this way.
       
    
-    
    
-
    - -
    +
    +
    +

    DLZ (Dynamically Loadable Zones)

    - -

    +

    DLZ (Dynamically Loadable Zones) is an extension to BIND 9 that allows zone data to be retrieved directly from an external database. There is no required format or schema. DLZ drivers exist for several different database backends including PostgreSQL, MySQL, and LDAP and can be written for any other.

    -

    +

    Historically, DLZ drivers had to be statically linked with the named binary and were turned on via a configure option at compile time (for example, "configure --with-dlz-ldap"). @@ -2276,7 +2090,7 @@ $ dnssec-signzone -E '' -S example.netcontrib/dlz/drivers are still linked this way.

    -

    +

    In BIND 9.8 and higher, it is possible to link some DLZ modules dynamically at runtime, via the DLZ "dlopen" driver, which acts as a generic wrapper around a shared object implementing the DLZ API. The @@ -2285,8 +2099,7 @@ $ dnssec-signzone -E '' -S example.netcontrib/dlz/drivers.

    - -

    +

    When the DLZ module provides data to named, it does so in text format. The response is converted to DNS wire format by named. This conversion, and the lack of any internal caching, places significant @@ -2297,22 +2110,20 @@ $ dnssec-signzone -E '' -S example.net - -

    +

    Configuring DLZ

    - -

    +

    A DLZ database is configured with a dlz statement in named.conf:

    - 
    +
         dlz example {
 	database "dlopen driver.so args";
 	search yes;
     };
     
    
-    
    
+
    
       This specifies a DLZ module to search when answering queries; the
       module is implemented in driver.so and is
       loaded at runtime by the dlopen DLZ driver.  Multiple
@@ -2322,11 +2133,11 @@ $ dnssec-signzone -E '' -S example.net
-    
    
+
    
       The search option in the above example can be
       omitted, because yes is the default value.
     
    
-    
    
+
    
       If search is set to no, then
       this DLZ module is not searched for the best
       match when a query is received.  Instead, zones in this DLZ must be
@@ -2336,7 +2147,7 @@ $ dnssec-signzone -E '' -S example.net
-    
    +
         dlz other {
 	database "dlopen driver.so args";
 	search no;
@@ -2347,12 +2158,11 @@ $ dnssec-signzone -E '' -S example.net
-
    -
    +
    +

    Sample DLZ Driver

    - -

    +

    For guidance in implementation of DLZ modules, the directory contrib/dlz/example contains a basic dynamically-linkable DLZ module--i.e., one which can be @@ -2361,25 +2171,25 @@ $ dnssec-signzone -E '' -S example.netdlz statement:

    - 
    +
         dlz other {
 	database "dlopen driver.so example.nil";
     };
     
    
-    
    
+
    
       In the above example, the module is configured to create a zone
       "example.nil", which can answer queries and AXFR requests, and
       accept DDNS updates.  At runtime, prior to any updates, the zone
       contains an SOA, NS, and a single A record at the apex:
     
    
-    
    +
      example.nil.  3600    IN      SOA     example.nil. hostmaster.example.nil. (
 					       123 900 600 86400 3600
 				       )
  example.nil.  3600    IN      NS      example.nil.
  example.nil.  1800    IN      A       10.53.0.1
     
    
-    
    
+
    
       The sample driver is capable of retrieving information about the
       querying client, and altering its response on the basis of this
       information.  To demonstrate this feature, the example driver
@@ -2390,21 +2200,19 @@ $ dnssec-signzone -E '' -S example.net
-    
    
+
    
       Documentation of the DLZ module API can be found in
       contrib/dlz/example/README.  This directory also
       contains the header file dlz_minimal.h, which
       defines the API and should be included by any dynamically-linkable
       DLZ module.
     
    
-
    - -
    +
    +

    DynDB (Dynamic Database)

    - -

    +

    DynDB is an extension to BIND 9 which, like DLZ (see the section called “DLZ (Dynamically Loadable Zones)”), allows zone data to be retrieved from an external database. Unlike DLZ, a DynDB module @@ -2416,31 +2224,29 @@ $ dnssec-signzone -E '' -S example.net -

    +

    A DynDB module supporting LDAP has been created by Red Hat and is available from https://fedorahosted.org/bind-dyndb-ldap/.

    -

    +

    A sample DynDB module for testing and developer guidance is included with the BIND source code, in the directory bin/tests/system/dyndb/driver.

    - -
    +

    Configuring DynDB

    - -

    +

    A DynDB database is configured with a dyndb statement in named.conf:

    - 
    +
         dyndb example "driver.so" {
         parameters
     };
     
    
-    
    
+
    
       The file driver.so is a DynDB module which
       implements the full DNS database API.  Multiple
       dyndb statements can be specified, to load
@@ -2450,17 +2256,16 @@ $ dnssec-signzone -E '' -S example.net
-    
    
+
    
       The parameters are passed as an opaque
       string to the DynDB module's initialization routine. Configuration
       syntax will differ depending on the driver.
     
    
-
    -
    +
    +

    Sample DynDB Module

    - -

    +

    For guidance in implementation of DynDB modules, the directory bin/tests/system/dyndb/driver. contains a basic DynDB module. @@ -2468,37 +2273,35 @@ $ dnssec-signzone -E '' -S example.netdyndb statement:

    - 
    +
         dyndb sample "sample.so" { example.nil. arpa. };
     
    
-    
    
+
    
       In the above example, the module is configured to create a zone
       "example.nil", which can answer queries and AXFR requests, and
       accept DDNS updates.  At runtime, prior to any updates, the zone
       contains an SOA, NS, and a single A record at the apex:
     
    
-    
    +
      example.nil.  86400    IN      SOA     example.nil. example.nil. (
                                                0 28800 7200 604800 86400
                                        )
  example.nil.  86400    IN      NS      example.nil.
  example.nil.  86400    IN      A       127.0.0.1
     
    
-    
    
+
    
       When the zone is updated dynamically, the DynDB module will determine
       whether the updated RR is an address (i.e., type A or AAAA) and if
       so, it will automatically update the corresponding PTR record in a
       reverse zone.  (Updates are not stored permanently; all updates are
       lost when the server is restarted.)
     
    
-
    - -
    +
    +

    Catalog Zones

    - -

    +

    A "catalog zone" is a special DNS zone that contains a list of other zones to be served, along with their configuration parameters. Zones listed in a catalog zone are called "member zones". @@ -2511,17 +2314,16 @@ $ dnssec-signzone -E '' -S example.net -

    +

    Catalog zones' format and behavior are specified as an internet draft for interoperability among DNS implementations. As of this release, the latest revision of the DNS catalog zones draft can be found here: https://datatracker.ietf.org/doc/draft-muks-dnsop-dns-catalog-zones/

    - -
    +

    Principle of Operation

    -

    +

    Normally, if a zone is to be served by a slave server, the named.conf file on the server must list the zone, or the zone must be added using rndc addzone. @@ -2530,13 +2332,13 @@ $ dnssec-signzone -E '' -S example.net -

    +

    A catalog zone is a way to ease this administrative burden. It is a DNS zone that lists member zones that should be served by slave servers. When a slave server receives an update to the catalog zone, it adds, removes, or reconfigures member zones based on the data received.

    -

    +

    To use a catalog zone, it must first be set up as a normal zone on the master and the on slave servers that will be configured to use it. It must also be added to a catalog-zones list @@ -2545,25 +2347,21 @@ $ dnssec-signzone -E '' -S example.netresponse-policy statement.)

    -

    +

    To use the catalog zone feature to serve a new member zone:

      -
    • -

      +

    • Set up the the member zone to be served on the master as normal. This could be done by editing named.conf, or by running rndc addzone. -

      -
      • -
    • -

      +

      • +

    • Add an entry to the catalog zone for the new member zone. This could be done by editing the catalog zone's master file and running rndc reload, or by updating the zone using nsupdate. -

      -
      • +

    The change to the catalog zone will be propagated from the master to all @@ -2575,7 +2373,7 @@ $ dnssec-signzone -E '' -S example.net -

    +

    Removing a member zone from a slave server requires nothing more than deleting the member zone's entry in the catalog zone. The change to the catalog zone is propagated to the slave server using the normal AXFR/IXFR @@ -2586,12 +2384,11 @@ $ dnssec-signzone -E '' -S example.netrndc delzone.)

    -
    - -
    +
    +

    Configuring Catalog Zones

    -

    +

    Catalog zones are configured with a catalog-zones statement in the options or view section of named.conf. For example, @@ -2605,24 +2402,24 @@ catalog-zones { min-update-interval 10; }; -

    +

    This statement specifies that the zone catalog.example is a catalog zone. This zone must be properly configured in the same view. In most configurations, it would be a slave zone.

    -

    +

    The options following the zone name are not required, and may be specified in any order:

    -

    +

    The default-masters option defines the default masters for member zones listed in a catalog zone. This can be overridden by options within a catalog zone. If no such options are included, then member zones will transfer their contents from the servers listed in this option.

    -

    +

    The in-memory option, if set to yes, causes member zones to be stored only in memory. This is functionally equivalent to configuring a slave zone without a file. @@ -2630,7 +2427,7 @@ catalog-zones { will be stored locally in a file whose name is automatically generated from the view name, catalog zone name, and member zone name.

    -

    +

    The zone-directory option causes local copies of member zones' master files (if in-memory is not set to yes) to be stored in the specified directory. @@ -2638,7 +2435,7 @@ catalog-zones { A non-absolute pathname in zone-directory is assumed to be relative to the working directory.

    -

    +

    The min-update-interval option sets the minimum interval between processing of updates to catalog zones, in seconds. If an update to a catalog zone (for example, via IXFR) happens less @@ -2646,24 +2443,23 @@ catalog-zones { recent update, then the changes will not be carried out until this interval has elapsed. The default is 5 seconds.

    -

    +

    Catalog zones are defined on a per-view basis. Configuring a non-empty catalog-zones statement in a view will automatically turn on allow-new-zones for that view. (Note: this means rndc addzone and rndc delzone will also work in any view that supports catalog zones.)

    -
    - -
    +
    +

    Catalog Zone format

    -

    +

    A catalog zone is a regular DNS zone; therefore, it has to have a single SOA and at least one NS record.

    -

    +

    A record stating the version of the catalog zone format is also required. If the version number listed is not supported by the server, then a catalog zone may not be used by that server. @@ -2673,57 +2469,57 @@ catalog.example. IN SOA . . 2016022901 900 600 86400 1 catalog.example. IN NS nsexample. version.catalog.example. IN TXT "1" -

    +

    Note that this record must have the domain name version.catalog-zone-name. This illustrates how the meaning of data stored in a catalog zone is indicated by the the domain name label immediately before the catalog zone domain.

    -

    +

    Catalog zone options can be set either globally for the whole catalog zone or for a single member zone. Global options override the settings in the configuration file and member zone options override global options.

    -

    +

    Global options are set at the apex of the catalog zone, e.g.: 

      masters.catalog.example.    IN AAAA 2001:db8::1
    -

    BIND currently supports the following options:

    -
      +

      BIND currently supports the following options:

      +
      • -

        A simple masters definition:

        - 
        +
        A simple masters definition:
        
+
         	 masters.catalog.example.    IN A 192.0.2.1
 	
        
-	
        
+
        
 	  This option defines a master server for the member zones - it
 	  can be either an A or AAAA record. If multiple masters are set the
 	  order in which they are used is random.
 	
        
-
        • +
      • -

        A masters with a TSIG key defined:

        - 
        +
        A masters with a TSIG key defined:
        
+
                  label.masters.catalog.example.     IN A 192.0.2.2
          label.masters.catalog.example.	    IN TXT "tsig_key_name"
         
        
-        
        
+
        
          This option defines a master server for the member zone with a TSIG
          key set. The TSIG key must be configured in the configuration file.
          label can be any valid DNS label.
         
        
-
        • +
      • -

        allow-query and +

        allow-query and allow-transfer ACLs:

        - 
        +
                  allow-query.catalog.example.	IN APL 1:10.0.0.1/24
          allow-transfer.catalog.example.	IN APL !1:10.0.0.1/32 1:10.0.0.0/24
         
        
-        
        
+
        
           These options are the equivalents of allow-query
           and allow-transfer in a zone declaration in the
           named.conf configuration file. The ACL is
@@ -2731,9 +2527,9 @@ version.catalog.example.    IN TXT "1"
           policy is to deny access.  For the syntax of the APL RR see RFC
           3123
         
        
-
        • +
      -

      +

      A member zone is added by including a PTR resource record in the zones sub-domain of the catalog zone. The record label is a SHA-1 hash @@ -2744,7 +2540,7 @@ version.catalog.example. IN TXT "1" 

       5960775ba382e7a4e09263fc06e7c00569b6a05c.zones.catalog.example. IN PTR domain.example.
      -

      +

      The hash is necessary to identify options for a specific member zone. The member zone-specific options are defined the same way as global options, but in the member zone subdomain: @@ -2755,33 +2551,31 @@ label.masters.5960775ba382e7a4e09263fc06e7c00569b6a05c.zones.catalog.example. IN label.masters.5960775ba382e7a4e09263fc06e7c00569b6a05c.zones.catalog.example. IN TXT "tsig_key" allow-query.5960775ba382e7a4e09263fc06e7c00569b6a05c.zones.catalog.example. IN APL 1:10.0.0.0/24 -

      +

      As would be expected, options defined for a specific zone override the global options defined in the catalog zone. These in turn override the global options defined in the catalog-zones statement in the configuration file.

      -

      +

      (Note that none of the global records an option will be inherited if any records are defined for that option for the specific zone. For example, if the zone had a masters record of type A but not AAAA, then it would not inherit the type AAAA record from the global option.)

      -
    - -
    +
    +

    IPv6 Support in BIND 9

    -

    +

    BIND 9 fully supports all currently defined forms of IPv6 name to address and address to name lookups. It will also use IPv6 addresses to make queries when running on an IPv6 capable system.

    - -

    +

    For forward lookups, BIND 9 supports only AAAA records. RFC 3363 deprecated the use of A6 records, and client-side support for A6 records was accordingly removed @@ -2791,8 +2585,7 @@ allow-query.5960775ba382e7a4e09263fc06e7c00569b6a05c.zones.catalog.example. IN A for A6 records, and accept zone transfer for a zone containing A6 records.

    - -

    +

    For IPv6 reverse lookups, BIND 9 supports the traditional "nibble" format used in the ip6.arpa domain, as well as the older, deprecated @@ -2807,39 +2600,33 @@ allow-query.5960775ba382e7a4e09263fc06e7c00569b6a05c.zones.catalog.example. IN A In particular, an authoritative BIND 9 name server will not load a zone file containing binary labels.

    - -

    +

    For an overview of the format and structure of IPv6 addresses, see the section called “IPv6 addresses (AAAA)”.

    - -
    +

    Address Lookups Using AAAA Records

    - -

    +

    The IPv6 AAAA record is a parallel to the IPv4 A record, and, unlike the deprecated A6 record, specifies the entire IPv6 address in a single record. For example,

    - 
     $ORIGIN example.com.
 host            3600    IN      AAAA    2001:db8::1
    - -

    +

    Use of IPv4-in-IPv6 mapped addresses is not recommended. If a host has an IPv4 address, use an A record, not a AAAA, with ::ffff:192.168.42.1 as the address.

    -
    -
    +
    +

    Address to Name Lookups Using Nibble Format

    - -

    +

    When looking up an address in nibble format, the address components are simply reversed, just as in IPv4, and ip6.arpa. is appended to the @@ -2848,16 +2635,14 @@ host 3600 IN AAAA 2001:db8::1 a host with address 2001:db8::1.

    - 
     $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0  14400   IN    PTR    (
                                     host.example.com. )
    - -
    -
    -
    +
    +
    +
    @@ -2875,6 +2660,6 @@ $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/Bv9ARM.ch05.html b/doc/arm/Bv9ARM.ch05.html index 19a8a5f365338a1377e30e3dbde197a86cf765f1..fafda38a82f5e7ca37bbf02119cdcb5fd3aaf4bf 100644 --- a/doc/arm/Bv9ARM.ch05.html +++ b/doc/arm/Bv9ARM.ch05.html @@ -10,7 +10,7 @@ Chapter 5. BIND 9 Configuration Reference - + @@ -96,8 +96,7 @@
    - -

    +

    BIND 9 configuration is broadly similar to BIND 8; however, there are a few new areas @@ -107,23 +106,20 @@ if they can be more efficiently implemented using the new features found in BIND 9.

    - -

    +

    BIND 4 configuration files can be converted to the new format using the shell script contrib/named-bootconf/named-bootconf.sh.

    -
    +

    Configuration File Elements

    - -

    +

    Following is a list of elements used throughout the BIND configuration file documentation:

    -
    - +
    @@ -528,87 +524,67 @@ -
    -
    -
    +
    +

    Address Match Lists

    - -
    +

    Syntax

    - 
    address_match_list = address_match_list_element ; ...
 
 address_match_list_element = [ ! ] ( ip_address | ip_prefix |
      key key_id | acl_name | { address_match_list } )
    - -
    -
    +
    +

    Definition and Usage

    - -

    +

    Address match lists are primarily used to determine access control for various server operations. They are also used in the listen-on and sortlist statements. The elements which constitute an address match list can be any of the following:

    -
      -
    • - an IP address (IPv4 or IPv6) -
      • -
    • - an IP prefix (in `/' notation) -
      • +
        +
      • an IP address (IPv4 or IPv6)
        • +
      • an IP prefix (in `/' notation)
      • - a key ID, as defined by the key statement - -
        • -
      • - the name of an address match list defined with +
        • +
      • the name of an address match list defined with the acl statement - -
        • -
      • - a nested address match list enclosed in braces -
        • + +
      • a nested address match list enclosed in braces
      - -

      +

      Elements can be negated with a leading exclamation mark (`!'), and the match list names "any", "none", "localhost", and "localnets" are predefined. More information on those names can be found in the description of the acl statement.

      - -

      +

      The addition of the key clause made the name of this syntactic element something of a misnomer, since security keys can be used to validate access without regard to a host or network address. Nonetheless, the term "address match list" is still used throughout the documentation.

      - -

      +

      When a given IP address or prefix is compared to an address match list, the comparison takes place in approximately O(1) time. However, key comparisons require that the list of keys be traversed until a matching key is found, and therefore may be somewhat slower.

      - -

      +

      The interpretation of a match depends on whether the list is being used for access control, defining listen-on ports, or in a sortlist, and whether the element was negated.

      - -

      +

      When used as an access control list, a non-negated match allows access and a negated match denies access. If there is no match, access is denied. The clauses @@ -628,8 +604,7 @@ server to refuse queries on any of the machine's addresses which do not match the list.

      - -

      +

      Order of insertion is significant. If more than one element in an ACL is found to match a given IP address or prefix, preference will be given to the one that came @@ -645,26 +620,22 @@ that problem by having 1.2.3.13 blocked by the negation, but all other 1.2.3.* hosts fall through.

      -
    -
    - -
    +
    +
    +

    Comment Syntax

    - -

    +

    The BIND 9 comment syntax allows for comments to appear anywhere that whitespace may appear in a BIND configuration file. To appeal to programmers of all kinds, they can be written in the C, C++, or shell/perl style.

    - -
    +

    Syntax

    - -

    +

    /* This is a BIND comment as in C */

    @@ -676,26 +647,25 @@ # and perl

    -
    -
    +
    +

    Definition and Usage

    - -

    +

    Comments may appear anywhere that whitespace may appear in a BIND configuration file.

    -

    +

    C-style comments start with the two characters /* (slash, star) and end with */ (star, slash). Because they are completely delimited with these characters, they can be used to comment only a portion of a line or to span multiple lines.

    -

    +

    C-style comments cannot be nested. For example, the following is not valid because the entire comment ends with the first */:

    -

    +

    /* This is the start of a comment.
@@ -706,15 +676,14 @@
 
    
 
           
    
-
-          
    
+
    
             C++-style comments start with the two characters // (slash,
             slash) and continue to the end of the physical line. They cannot
             be continued across multiple physical lines; to have one logical
             comment span multiple lines, each line must use the // pair.
             For example:
           
    
-          
    
+
    
 
 
    
 
    // This is the start of a comment.  The next line
@@ -724,15 +693,14 @@
 
    
 
           
    
-          
    
+
    
             Shell-style (or perl-style, if you prefer) comments start
             with the character # (number sign)
             and continue to the end of the
             physical line, as in C++ comments.
             For example:
           
    
-
-          
    
+
    
 
 
    
 
    # This is the start of a comment.  The next line
@@ -742,25 +710,22 @@
 
    
 
           
    
-
-          
    
+
    
 
    Warning
    
-            
    
+
    
               You cannot use the semicolon (`;') character
               to start a comment such as you would in a zone file. The
               semicolon indicates the end of a configuration
               statement.
             
    
-          
    
-        
    
-
    -
    - -
    +
    +
    +
    +
    +

    Configuration File Grammar

    - -

    +

    A BIND 9 configuration consists of statements and comments. Statements end with a semicolon. Statements and comments are the @@ -768,13 +733,10 @@ statements contain a block of sub-statements, which are also terminated with a semicolon.

    - -

    +

    The following statements are supported:

    - -
    - +
    @@ -922,40 +884,33 @@ -
    -
    - -

    +

    +

    The logging and options statements may only occur once per configuration.

    - -
    +

    acl Statement Grammar

    - 
    +
     acl string { address_match_element; ... };
 
    
-
    -
    +
    +

    acl Statement Definition and Usage

    - -

    +

    The acl statement assigns a symbolic name to an address match list. It gets its name from a primary use of address match lists: Access Control Lists (ACLs).

    - -

    +

    The following ACLs are built-in:

    - -
    - +
    @@ -1015,13 +970,12 @@ -
    -
    -
    -
    +
    +
    +

    controls Statement Grammar

    - 
    +
     controls {
 	inet ( ipv4_address | ipv6_address |
 	    * ) [ port ( integer | * ) ] allow
@@ -1034,22 +988,19 @@
 	    boolean ];
 };
 
    
-
    - -
    +
    +

    controls Statement Definition and Usage

    - -

    +

    The controls statement declares control channels to be used by system administrators to control the operation of the name server. These control channels are used by the rndc utility to send commands to and retrieve non-DNS results from a name server.

    - -

    +

    An inet control channel is a TCP socket listening at the specified ip_port on the specified ip_addr, which can be an IPv4 or IPv6 @@ -1062,13 +1013,11 @@ using the loopback address (127.0.0.1 or ::1) is recommended for maximum security.

    - -

    +

    If no port is specified, port 953 is used. The asterisk "*" cannot be used for ip_port.

    - -

    +

    The ability to issue commands over the control channel is restricted by the allow and keys clauses. @@ -1078,8 +1027,7 @@ elements of the address_match_list are ignored.

    - -

    +

    A unix control channel is a UNIX domain socket listening at the specified path in the file system. Access to the socket is specified by the perm, @@ -1088,8 +1036,7 @@ (perm) are applied to the parent directory as the permissions on the socket itself are ignored.

    - -

    +

    The primary authorization mechanism of the command channel is the key_list, which contains a list of key_ids. @@ -1098,8 +1045,7 @@ See Remote Name Daemon Control application in the section called “Administrative Tools”) for information about configuring keys in rndc.

    - -

    +

    If the read-only clause is enabled, the control channel is limited to the following set of read-only commands: nta -dump, @@ -1109,8 +1055,7 @@ read-only is not enabled and the control channel allows read-write access.

    - -

    +

    If no controls statement is present, named will set up a default control channel listening on the loopback address 127.0.0.1 @@ -1124,8 +1069,7 @@ To create a rndc.key file, run rndc-confgen -a.

    - -

    +

    The rndc.key feature was created to ease the transition of systems from BIND 8, which did not have digital signatures on its command channel @@ -1138,8 +1082,7 @@ command rndc-confgen -a after BIND 9 is installed.

    - -

    +

    Since the rndc.key feature is only intended to allow the backward-compatible usage of BIND 8 configuration files, this @@ -1160,25 +1103,21 @@ readable by a group that contains the users who should have access.

    - -

    +

    To disable the command channel, use an empty controls statement: controls { };.

    - -
    -
    +
    +

    include Statement Grammar

    - - 
    include filename;
    -
    -
    +
    include filename;
    +
    +

    include Statement Definition and Usage

    - -

    +

    The include statement inserts the specified file at the point where the include statement is encountered. The include @@ -1188,32 +1127,28 @@ others. For example, the statement could include private keys that are readable only by the name server.

    - -
    -
    +
    +

    key Statement Grammar

    - 
    +
     key string {
 	algorithm string;
 	secret string;
 };
 
    
-
    - -
    +
    +

    key Statement Definition and Usage

    - -

    +

    The key statement defines a shared secret key for use with TSIG (see the section called “TSIG”) or the command channel (see the section called “controls Statement Definition and Usage”).

    - -

    +

    The key statement can occur at the top level of the configuration file or inside a view @@ -1224,8 +1159,7 @@ Usage”) must be defined at the top level.

    - -

    +

    The key_id, also known as the key name, is a domain name uniquely identifying the key. It can be used in a server @@ -1234,8 +1168,7 @@ verify that incoming requests have been signed with a key matching this name, algorithm, and secret.

    - -

    +

    The algorithm_id is a string that specifies a security/authentication algorithm. The named server supports hmac-md5, @@ -1249,12 +1182,11 @@ to be used by the algorithm, and is treated as a Base64 encoded string.

    - -
    -
    +
    +

    logging Statement Grammar

    - 
    +
     logging {
 	category string { string; ... };
 	channel string {
@@ -1271,13 +1203,11 @@
 	};
 };
 
    
-
    - -
    +
    +

    logging Statement Definition and Usage

    - -

    +

    The logging statement configures a wide variety of logging options for the name server. Its channel phrase @@ -1285,33 +1215,29 @@ a name that can then be used with the category phrase to select how various classes of messages are logged.

    -

    +

    Only one logging statement is used to define as many channels and categories as are wanted. If there is no logging statement, the logging configuration will be:

    - 
    logging {
      category default { default_syslog; default_debug; };
      category unmatched { null; };
 };
    - -

    +

    If named is started with the -L option, it logs to the specified file at startup, instead of using syslog. In this case the logging configuration will be:

    - 
    logging {
      category default { default_logfile; default_debug; };
      category unmatched { null; };
 };
    - -

    +

    In BIND 9, the logging configuration is only established when the entire configuration file has been parsed. In BIND 8, it was @@ -1322,17 +1248,14 @@ channels, or to standard error if the -g option was specified.

    - -
    +

    The channel Phrase

    - -

    +

    All log output goes to one or more channels; you can make as many of them as you want.

    - -

    +

    Every channel definition must include a destination clause that says whether messages selected for the channel go to a file, to a particular syslog facility, to the standard error stream, or are @@ -1343,14 +1266,12 @@ category name and/or severity level (the default is not to include any).

    - -

    +

    The null destination clause causes all messages sent to the channel to be discarded; in that case, other options for the channel are meaningless.

    - -

    +

    The file destination clause directs the channel to a disk file. It can include additional arguments to specify how large the file is allowed to @@ -1360,8 +1281,7 @@ (versions), and the format to use for naming backup versions (suffix).

    - -

    +

    The size option is used to limit log file growth. If the file ever exceeds the specified size, then named will stop writing to the @@ -1373,7 +1293,7 @@ removes or truncates the log to less than the maximum size. The default behavior is not to limit the size of the file.

    -

    +

    File rolling only occurs when the file exceeds the size specified with the size option. No backup versions are kept by default; any existing @@ -1382,7 +1302,7 @@ how many backup versions of the file should be kept. If set to unlimited, there is no limit.

    -

    +

    The suffix option can be set to either increment or timestamp. If set to @@ -1405,21 +1325,18 @@ whereupon a new filename.log is opened.

    - -

    +

    Example usage of the size, versions, and suffix options:

    - 
    channel an_example_channel {
     file "example.log" versions 3 size 20m suffix increment;
     print-time yes;
     print-category yes;
 };
    - -

    +

    The syslog destination clause directs the channel to the system log. Its argument is a @@ -1441,10 +1358,10 @@ only uses two arguments to the openlog() function, then this clause is silently ignored.

    -

    +

    On Windows machines syslog messages are directed to the EventViewer.

    -

    +

    The severity clause works like syslog's "priorities", except that they can also be used if you are writing straight to a file rather than using syslog. @@ -1453,7 +1370,7 @@ levels will be accepted.

    -

    +

    If you are using syslog, then the syslog.conf priorities will also determine what eventually passes through. For example, defining a channel facility and severity as daemon and debug but @@ -1465,8 +1382,7 @@ then syslogd would print all messages it received from the channel.

    - -

    +

    The stderr destination clause directs the channel to the server's standard error stream. This is intended @@ -1475,8 +1391,7 @@ example when debugging a configuration.

    - -

    +

    The server can supply extensive debugging information when it is in debugging mode. If the server's global debug level is greater @@ -1490,21 +1405,19 @@ notrace. All debugging messages in the server have a debug level, and higher debug levels give more detailed output. Channels that specify a specific debug severity, for example:

    - 
    channel specific_debug_level {
     file "foo";
     severity debug 3;
 };
    - -

    +

    will get debugging output of level 3 or less any time the server is in debugging mode, regardless of the global debugging level. Channels with dynamic severity use the server's global debug level to determine what messages to print.

    -

    +

    print-time can be set to yes, no, or a time format specifier, which may be one of @@ -1520,14 +1433,14 @@ notrace. All debugging messages in the server have a debug are logged in ISO8601 format, with time zone set to UTC. The default is no.

    -

    +

    print-time may be specified for a syslog channel, but it is usually pointless since syslog also logs the date and time.

    -

    +

    If print-category is requested, then the category of the message will be logged as well. Finally, if print-severity is @@ -1538,18 +1451,15 @@ notrace. All debugging messages in the server have a debug three print- options are on:

    - -

    +

    28-Feb-2000 15:05:32.863 general: notice: running

    - -

    +

    If buffered has been turned on the output to files will not be flushed after each log entry. By default all log messages are flushed.

    - -

    +

    There are four predefined channels that are used for named's default logging as follows. If named is started with the @@ -1558,7 +1468,6 @@ notrace. All debugging messages in the server have a debug How they are used is described in the section called “The category Phrase”.

    - 
    channel default_syslog {
     // send to syslog's daemon facility
     syslog daemon;
@@ -1596,8 +1505,7 @@ channel default_logfile {
     severity dynamic;
 };
    - -

    +

    The default_debug channel has the special property that it only produces output when the server's debug @@ -1605,8 +1513,7 @@ channel default_logfile { nonzero. It normally writes to a file called named.run in the server's working directory.

    - -

    +

    For security reasons, when the -u command line option is used, the named.run file is created only after named has @@ -1617,20 +1524,17 @@ channel default_logfile { option to specify a default logfile, or the -g option to log to standard error which you can redirect to a file.

    - -

    +

    Once a channel is defined, it cannot be redefined. Thus you cannot alter the built-in channels directly, but you can modify the default logging by pointing categories at channels you have defined.

    -
    - -
    +
    +

    The category Phrase

    - -

    +

    There are many categories, so you can send the logs you want to see wherever you want, without seeing logs you don't want. If you don't specify a list of channels for a category, then log @@ -1639,24 +1543,19 @@ channel default_logfile { instead. If you don't specify a default category, the following "default default" is used:

    - 
    category default { default_syslog; default_debug; };
    - -

    +

    If you start named with the -L option then the default category is:

    - 
    category default { default_logfile; default_debug; };
    - -

    +

    As an example, let's say you want to log security events to a file, but you also want keep the default logging behavior. You'd specify the following:

    - 
    channel my_security_channel {
     file "my_security_file";
     severity info;
@@ -1666,22 +1565,18 @@ category security {
     default_syslog;
     default_debug;
 };
    - -

    +

    To discard all messages in a category, specify the null channel:

    - 
    category xfer-out { null; };
 category notify { null; };
    - -

    +

    Following are the available categories and brief descriptions of the types of log information they contain. More categories may be added in future BIND releases.

    -
    - +
    @@ -2096,13 +1991,12 @@ category notify { null; }; -
    +
    -
    -
    +

    The query-errors Category

    -

    +

    The query-errors category is specifically intended for debugging purposes: To identify why and how specific queries result in responses which @@ -2110,15 +2004,14 @@ category notify { null; }; Messages of this category are therefore only logged with debug levels.

    - -

    +

    At the debug levels of 1 or higher, each response with the rcode of SERVFAIL is logged as follows:

    -

    +

    client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880

    -

    +

    This means an error resulting in SERVFAIL was detected at line 3880 of source file query.c. @@ -2126,13 +2019,13 @@ category notify { null; }; help identify the cause of SERVFAIL for an authoritative server.

    -

    +

    At the debug levels of 2 or higher, detailed context information of recursive resolutions that resulted in SERVFAIL is logged. The log message will look like as follows:

    -

    +

    @@ -2143,14 +2036,14 @@ badresp:1,adberr:0,findfail:0,valfail:0]

    -

    +

    The first part before the colon shows that a recursive resolution for AAAA records of www.example.com completed in 30.000183 seconds and the final result that led to the SERVFAIL was determined at line 2970 of source file resolver.c.

    -

    +

    The following part shows the detected final result and the latest result of DNSSEC validation. The latter is always success when no validation attempt @@ -2160,7 +2053,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] to a timeout in 30 seconds. DNSSEC validation was probably not attempted.

    -

    +

    The last part enclosed in square brackets shows statistics information collected for this particular resolution attempt. @@ -2170,9 +2063,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] The meaning of the other fields is summarized in the following table.

    - -
    - +
    @@ -2311,16 +2202,15 @@ badresp:1,adberr:0,findfail:0,valfail:0] -
    -
    -

    +

    +

    At the debug levels of 3 or higher, the same messages as those at the debug 1 level are logged for other errors than SERVFAIL. Note that negative responses such as NXDOMAIN are not regarded as errors here.

    -

    +

    At the debug levels of 4 or higher, the same messages as those at the debug 2 level are logged for other errors than SERVFAIL. @@ -2329,41 +2219,36 @@ badresp:1,adberr:0,findfail:0,valfail:0] This is because any unexpected results can be difficult to debug in the recursion case.

    -
    -
    - -
    +
    +
    +

    masters Statement Grammar

    - 
    +
     masters string [ port integer ] [ dscp
     integer ] { ( masters | ipv4_address [
     port integer ] | ipv6_address [ port
     integer ] ) [ key string ]; ... };
 
    
-
    - -
    +
    +

    masters Statement Definition and Usage

    - -

    masters +

    masters lists allow for a common set of masters to be easily used by multiple stub and slave zones in their masters or also-notify lists.

    -
    - -
    +
    +

    options Statement Grammar

    - -

    +

    This is the grammar of the options statement in the named.conf file:

    - 
    +
     options {
 	allow-new-zones boolean;
 	allow-notify { address_match_element; ... };
@@ -2415,9 +2300,9 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 	coresize ( default | unlimited | sizeval );
 	datasize ( default | unlimited | sizeval );
 	deny-answer-addresses { address_match_element; ... } [
-	    except-from { quoted_string; ... } ];
-	deny-answer-aliases { quoted_string; ... } [ except-from {
-	    quoted_string; ... } ];
+	    except-from { string; ... } ];
+	deny-answer-aliases { string; ... } [ except-from { string; ...
+	    } ];
 	dialup ( notify | notify-passive | passive | refresh | boolean );
 	directory quoted_string;
 	disable-algorithms string { string;
@@ -2448,14 +2333,12 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 	dnssec-secure-to-insecure boolean;
 	dnssec-update-mode ( maintain | no-resign );
 	dnssec-validation ( yes | no | auto );
-	dnstap { ( all | auth | client | forwarder |
-	    resolver ) [ ( query | response ) ]; ... };
-	dnstap-identity ( quoted_string | none |
-	    hostname );
-	dnstap-output ( file | unix ) quoted_string [
-	    size ( unlimited | size ) ] [ versions (
-	    unlimited | integer ) ] [ suffix ( increment
-	    | timestamp ) ];
+	dnstap { ( all | auth | client | forwarder | resolver ) [ ( query |
+	    response ) ]; ... };
+	dnstap-identity ( quoted_string | none | hostname );
+	dnstap-output ( file | unix ) quoted_string [ size ( unlimited |
+	    size ) ] [ versions ( unlimited | integer ) ] [ suffix (
+	    increment | timestamp ) ];
 	dnstap-version ( quoted_string | none );
 	dscp integer;
 	dual-stack-servers [ port integer ] { ( quoted_string [ port
@@ -2554,7 +2437,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 	preferred-glue string;
 	prefetch integer [ integer ];
 	provide-ixfr boolean;
-	qname-minimization ( strict | relaxed | disabled );
+	qname-minimization ( strict | relaxed | disabled | off );
 	query-source ( ( [ address ] ( ipv4_address | * ) [ port (
 	    integer | * ) ] ) | ( [ [ address ] ( ipv4_address | * ) ]
 	    port ( integer | * ) ) ) [ dscp integer ];
@@ -2605,7 +2488,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 	    nsip-enable boolean ] [ nsdname-enable boolean ] [
 	    dnsrps-enable boolean ] [ dnsrps-options { unspecified-text
 	    } ];
-	root-delegation-only [ exclude { quoted_string; ... } ];
+	root-delegation-only [ exclude { string; ... } ];
 	root-key-sentinel boolean;
 	rrset-order { [ class string ] [ type string ] [ name
 	    quoted_string ] string string; ... };
@@ -2655,20 +2538,19 @@ badresp:1,adberr:0,findfail:0,valfail:0]
 	use-v4-udp-ports { portrange; ... };
 	use-v6-udp-ports { portrange; ... };
 	v6-bias integer;
+	validate-except { string; ... };
 	version ( quoted_string | none );
 	zero-no-soa-ttl boolean;
 	zero-no-soa-ttl-cache boolean;
 	zone-statistics ( full | terse | none | boolean );
 };
 
    
-
    - -
    +
    +

    options Statement Definition and Usage

    - -

    +

    The options statement sets up global options to be used by BIND. This statement @@ -2677,11 +2559,10 @@ badresp:1,adberr:0,findfail:0,valfail:0] statement, an options block with each option set to its default will be used.

    - -
    +
    attach-cache
    -

    +

    Allows multiple views to share a single cache database. Each view has its own cache database by default, but @@ -2690,15 +2571,13 @@ badresp:1,adberr:0,findfail:0,valfail:0] share a single cache to save memory and possibly improve resolution efficiency by using this option.

    - -

    +

    The attach-cache option may also be specified in view statements, in which case it overrides the global attach-cache option.

    - -

    +

    The cache_name specifies the cache to be shared. When the named server configures @@ -2708,16 +2587,14 @@ badresp:1,adberr:0,findfail:0,valfail:0] The rest of the views will simply refer to the already created cache.

    - -

    +

    One common configuration to share a cache would be to allow all views to share a single cache. This can be done by specifying the attach-cache as a global option with an arbitrary name.

    - -

    +

    Another possible operation is to allow a subset of all views to share a cache while the others to retain their own caches. @@ -2726,7 +2603,6 @@ badresp:1,adberr:0,findfail:0,valfail:0] attach-cache option as a view A (or B)'s option, referring to the other view name:

    - 
       view "A" {
     // this view has its own cache
@@ -2741,8 +2617,7 @@ badresp:1,adberr:0,findfail:0,valfail:0]
     ...
   };
    - -

    +

    Views that share a cache must have the same policy on configurable parameters that may affect caching. The current implementation requires the following @@ -2758,8 +2633,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] max-cache-size, and zero-no-soa-ttl.

    - -

    +

    Note that there may be other parameters that may cause confusion if they are inconsistent for different views that share a single cache. @@ -2771,10 +2645,9 @@ badresp:1,adberr:0,findfail:0,valfail:0] configuration differences in different views do not cause disruption with a shared cache.

    -
    +
    directory
    -
    -

    +

    The working directory of the server. Any non-absolute pathnames in the configuration file will be taken as relative to this directory. The default @@ -2786,11 +2659,10 @@ badresp:1,adberr:0,findfail:0,valfail:0] should be an absolute path, and must be writable by the effective user ID of the named process. -

    -
    +

    dnstap
    -

    +

    dnstap is a fast, flexible method for capturing and logging DNS traffic. Developed by Robert Edmonds at Farsight Security, Inc., and supported @@ -2805,13 +2677,13 @@ badresp:1,adberr:0,findfail:0,valfail:0] by Google, Inc.; see https://developers.google.com/protocol-buffers).

    -

    +

    To enable dnstap at compile time, the fstrm and protobuf-c libraries must be available, and BIND must be configured with --enable-dnstap.

    -

    +

    The dnstap option is a bracketed list of message types to be logged. These may be set differently for each view. Supported types are client, @@ -2820,13 +2692,13 @@ badresp:1,adberr:0,findfail:0,valfail:0] all will cause all dnstap messages to be logged, regardless of type.

    -

    +

    Each type may take an additional argument to indicate whether to log query messages or response messages; if not specified, both queries and responses are logged.

    -

    +

    Example: To log all authoritative queries and responses, recursive client responses, and upstream queries sent by the resolver, use: @@ -2839,76 +2711,63 @@ badresp:1,adberr:0,findfail:0,valfail:0]

    -

    +

    Logged dnstap messages can be parsed using the dnstap-read utility (see dnstap-read(1) for details).

    -

    +

    For more information on dnstap, see http://dnstap.info.

    -

    +

    The fstrm library has a number of tunables that are exposed in named.conf, and can be modified if necessary to improve performance or prevent loss of data. These are:

    -
      +
      • - fstrm-set-buffer-hint: The threshold number of bytes to accumulate in the output buffer before forcing a buffer flush. The minimum is 1024, the maximum is 65536, and the default is 8192. - -
        • +
      • - fstrm-set-flush-timeout: The number of seconds to allow unflushed data to remain in the output buffer. The minimum is 1 second, the maximum is 600 seconds (10 minutes), and the default is 1 second. - -
        • +
      • - fstrm-set-output-notify-threshold: The number of outstanding queue entries to allow on an input queue before waking the I/O thread. The minimum is 1 and the default is 32. - -
        • +
      • - fstrm-set-output-queue-model: Controls the queuing semantics to use for queue objects. The default is mpsc (multiple producer, single consumer); the other option is spsc (single producer, single consumer). - -
        • +
      • - fstrm-set-input-queue-size: The number of queue entries to allocate for each input queue. This value must be a power of 2. The minimum is 2, the maximum is 16384, and the default is 512. - -
        • +
      • - fstrm-set-output-queue-size: The number of queue entries to allocate for each output queue. The minimum is 2, the maximum is system-dependent and based on IOV_MAX, and the default is 64. - -
        • +
      • - fstrm-set-reopen-interval: The number of seconds to wait between attempts to reopen a closed output stream. The minimum is 1 second, @@ -2916,25 +2775,24 @@ badresp:1,adberr:0,findfail:0,valfail:0] is 5 seconds. For convenience, TTL-style time unit suffixes may be used to specify the value. - -
        • +
      -

      +

      Note that all of the above minimum, maximum, and default values are set by the libfstrm library, and may be subject to change in future versions of the library. See the libfstrm documentation for more information.

      -
    +
    dnstap-output
    -

    +

    Configures the path to which the dnstap frame stream will be sent if dnstap is enabled at compile time and active.

    -

    +

    The first argument is either file or unix, indicating whether the destination is a file or a UNIX domain socket. The second argument @@ -2945,7 +2803,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] (provided with libfstrm) is listening on the socket.)

    -

    +

    If the first argument is file, then up to three additional options can be added: size indicates the size to which a @@ -2962,7 +2820,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] The default is to allow dnstap log files to grow to any size without rolling.

    -

    +

    dnstap-output can only be set globally in options. Currently, it can only be set once while named is running; @@ -2970,29 +2828,24 @@ badresp:1,adberr:0,findfail:0,valfail:0] rndc reload or rndc reconfig.

    -
    +
    dnstap-identity
    -
    -

    +

    Specifies an identity string to send in dnstap messages. If set to hostname, which is the default, the server's hostname will be sent. If set to none, no identity string will be sent. -

    -
    +

    dnstap-version
    -
    -

    +

    Specifies a version string to send in dnstap messages. The default is the version number of the BIND release. If set to none, no version string will be sent. -

    -
    +

    geoip-directory
    -
    -

    +

    Specifies the directory containing GeoIP .dat database files for GeoIP initialization. By default, this option is unset @@ -3001,11 +2854,9 @@ badresp:1,adberr:0,findfail:0,valfail:0] (For details, see the section called “acl Statement Definition and Usage” about the geoip ACL.) -

    -
    +

    key-directory
    -
    -

    +

    When performing dynamic update of secure zones, the directory where the public and private DNSSEC key files should be found, if different than the current working @@ -3014,11 +2865,10 @@ badresp:1,adberr:0,findfail:0,valfail:0] bind.keys, rndc.key or session.key.) -

    -
    +

    lmdb-mapsize
    -

    +

    When named is built with liblmdb, this option sets a maximum size for the memory map of the new-zone database (NZD) in LMDB database format. @@ -3027,7 +2877,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] Note that this is not the NZD database file size, but the largest size that the database may grow to.

    -

    +

    Because the database file is memory mapped, its size is limited by the address space of the named process. The default of 32 megabytes was chosen to be usable with @@ -3037,17 +2887,17 @@ badresp:1,adberr:0,findfail:0,valfail:0] ought to be able to hold configurations of about 100,000 zones.

    -
    +
    managed-keys-directory
    -

    +

    Specifies the directory in which to store the files that track managed DNSSEC keys. By default, this is the working directory. The directory must be writable by the effective user ID of the named process.

    -

    +

    If named is not configured to use views, then managed keys for the server will be tracked in a single file called managed-keys.bind. @@ -3058,39 +2908,34 @@ badresp:1,adberr:0,findfail:0,valfail:0] followed by the extension .mkeys.

    -

    +

    (Note: in previous releases, file names for views always used the SHA256 hash of the view name. To ensure compatibility after upgrade, if a file using the old name format is found to exist, it will be used instead of the new format.)

    -
    +
    new-zones-directory
    -
    -

    +

    Specifies the directory in which to store the configuration parameters for zones added via rndc addzone. By default, this is the working directory. If set to a relative path, it will be relative to the working directory. The directory must be writable by the effective user ID of the named process. -

    -
    +

    named-xfer
    -
    -

    +

    This option is obsolete. It was used in BIND 8 to specify the pathname to the named-xfer program. In BIND 9, no separate named-xfer program is needed; its functionality is built into the name server. -

    -
    +

    qname-minimization
    -
    -

    +

    This option controls QNAME minimization behaviour in the BIND resolver. When set to strict, BIND will follow the QNAME minimization algorithm to @@ -3103,20 +2948,16 @@ badresp:1,adberr:0,findfail:0,valfail:0] QNAME minimization completely. The current default is relaxed, but it might be changed to strict in a future release. -

    -
    +

    tkey-gssapi-keytab
    -
    -

    +

    The KRB5 keytab file to use for GSS-TSIG updates. If this option is set and tkey-gssapi-credential is not set, then updates will be allowed with any key matching a principal in the specified keytab. -

    -
    +

    tkey-gssapi-credential
    -
    -

    +

    The security credential with which the server should authenticate keys requested by the GSS-TSIG protocol. Currently only Kerberos 5 authentication is available @@ -3129,11 +2970,9 @@ badresp:1,adberr:0,findfail:0,valfail:0] To use GSS-TSIG, tkey-domain must also be set if a specific keytab is not set with tkey-gssapi-keytab. -

    -
    +

    tkey-domain
    -
    -

    +

    The domain appended to the names of all shared keys generated with TKEY. When a client requests a TKEY exchange, @@ -3149,11 +2988,9 @@ badresp:1,adberr:0,findfail:0,valfail:0] "_tkey.domainname". If you are using GSS-TSIG, this variable must be defined, unless you specify a specific keytab using tkey-gssapi-keytab. -

    -
    +

    tkey-dhkey
    -
    -

    +

    The Diffie-Hellman key used by the server to generate shared keys with clients using the Diffie-Hellman mode @@ -3162,34 +2999,27 @@ badresp:1,adberr:0,findfail:0,valfail:0] public and private keys from files in the working directory. In most cases, the key_name should be the server's host name. -

    -
    +

    cache-file
    -
    -

    +

    This is for testing only. Do not use. -

    -
    +

    dump-file
    -
    -

    +

    The pathname of the file the server dumps the database to when instructed to do so with rndc dumpdb. If not specified, the default is named_dump.db. -

    -
    +

    memstatistics-file
    -
    -

    +

    The pathname of the file the server writes memory usage statistics to on exit. If not specified, the default is named.memstats. -

    -
    +

    lock-file
    -

    +

    The pathname of a file on which named will attempt to acquire a file lock when starting up for the first time; if unsuccessful, the server will @@ -3197,7 +3027,7 @@ badresp:1,adberr:0,findfail:0,valfail:0] server is already running. If not specified, the default is /var/run/named/named.lock.

    -

    +

    Specifying lock-file none disables the use of a lock file. lock-file is ignored if named was run using the -X @@ -3207,10 +3037,9 @@ badresp:1,adberr:0,findfail:0,valfail:0] reconfigured; it is only effective when the server is first started up.

    -
    +
    pid-file
    -
    -

    +

    The pathname of the file the server writes its process ID in. If not specified, the default is /var/run/named/named.pid. @@ -3222,51 +3051,41 @@ badresp:1,adberr:0,findfail:0,valfail:0] is a keyword, not a filename, and therefore is not enclosed in double quotes. -

    -
    +

    recursing-file
    -
    -

    +

    The pathname of the file the server dumps the queries that are currently recursing when instructed to do so with rndc recursing. If not specified, the default is named.recursing. -

    -
    +

    statistics-file
    -
    -

    +

    The pathname of the file the server appends statistics to when instructed to do so using rndc stats. If not specified, the default is named.stats in the server's current directory. The format of the file is described in the section called “The Statistics File”. -

    -
    +

    bindkeys-file
    -
    -

    +

    The pathname of a file to override the built-in trusted keys provided by named. See the discussion of dnssec-validation for details. If not specified, the default is /etc/bind.keys. -

    -
    +

    secroots-file
    -
    -

    +

    The pathname of the file the server dumps security roots to when instructed to do so with rndc secroots. If not specified, the default is named.secroots. -

    -
    +

    session-keyfile
    -
    -

    +

    The pathname of the file into which to write a TSIG session key generated by named for use by nsupdate -l. If not specified, the @@ -3276,27 +3095,21 @@ badresp:1,adberr:0,findfail:0,valfail:0] update-policy statement's local option for more information about this feature.) -

    -
    +

    session-keyname
    -
    -

    +

    The key name to use for the TSIG session key. If not specified, the default is "local-ddns". -

    -
    +

    session-keyalg
    -
    -

    +

    The algorithm to use for the TSIG session key. Valid values are hmac-sha1, hmac-sha224, hmac-sha256, hmac-sha384, hmac-sha512 and hmac-md5. If not specified, the default is hmac-sha256. -

    -
    +

    port
    -
    -

    +

    The UDP/TCP port number the server uses for receiving and sending DNS protocol traffic. The default is 53. This option is mainly intended for server @@ -3304,26 +3117,23 @@ badresp:1,adberr:0,findfail:0,valfail:0] a server using a port other than 53 will not be able to communicate with the global DNS. -

    -
    +

    dscp
    -
    -

    +

    The global Differentiated Services Code Point (DSCP) value to classify outgoing DNS traffic on operating systems that support DSCP. Valid values are 0 through 63. It is not configured by default. -

    -
    +

    random-device
    -

    +

    Specifies a source of entropy to be used by the server. This is a device or file from which to read entropy. If it is a file, operations requiring entropy will fail when the file has been exhausted.

    -

    +

    Entropy is needed for cryptographic operations such as TKEY transactions, dynamic update of signed zones, and generation of TSIG session keys. It is also used for @@ -3332,47 +3142,45 @@ badresp:1,adberr:0,findfail:0,valfail:0] randomness such as generation of DNS message transaction ID's.

    -

    +

    If random-device is not specified, or if it is set to none, entropy will be read from the random number generation function supplied by the cryptographic library with which BIND was linked (i.e. OpenSSL or a PKCS#11 provider).

    -

    +

    The random-device option takes effect during the initial configuration load at server startup time and is ignored on subsequent reloads.

    -
    +
    preferred-glue
    -
    -

    +

    If specified, the listed type (A or AAAA) will be emitted before other glue in the additional section of a query response. The default is to prefer A records when responding to queries that arrived via IPv4 and AAAA when responding to queries that arrived via IPv6. -

    -
    +

    root-delegation-only
    -

    +

    Turn on enforcement of delegation-only in TLDs (top level domains) and root zones with an optional exclude list.

    -

    +

    DS queries are expected to be made to and be answered by delegation only zones. Such queries and responses are treated as an exception to delegation-only processing and are not converted to NXDOMAIN responses provided a CNAME is not discovered at the query name.

    -

    +

    If a delegation only zone server also serves a child zone it is not always possible to determine whether an answer comes from the delegation only zone or the @@ -3388,26 +3196,24 @@ badresp:1,adberr:0,findfail:0,valfail:0] all these checks there is still a possibility of false negatives when a child zone is being served.

    -

    +

    Similarly false positives can arise from empty nodes (no records at the name) in the delegation only zone when the query type is not ANY.

    -

    +

    Note some TLDs are not delegation only (e.g. "DE", "LV", "US" and "MUSEUM"). This list is not exhaustive.

    - 
     options {
         root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
 };
    - -
    +
    disable-algorithms
    -

    +

    Disable the specified DNSSEC algorithms at and below the specified name. Multiple disable-algorithms @@ -3415,15 +3221,15 @@ options { Only the best match disable-algorithms clause will be used to determine which algorithms are used.

    -

    +

    If all supported algorithms are disabled, the zones covered by the disable-algorithms will be treated as insecure.

    -
    +
    disable-ds-digests
    -

    +

    Disable the specified DS/DLV digest types at and below the specified name. Multiple disable-ds-digests @@ -3431,15 +3237,15 @@ options { Only the best match disable-ds-digests clause will be used to determine which digest types are used.

    -

    +

    If all supported digest types are disabled, the zones covered by the disable-ds-digests will be treated as insecure.

    -
    +
    dnssec-lookaside
    -

    +

    When set, dnssec-lookaside provides the validator with an alternate method to validate DNSKEY records at the top of a zone. When a DNSKEY is at or @@ -3451,12 +3257,12 @@ options { record validates a DNSKEY (similarly to the way a DS record does) the DNSKEY RRset is deemed to be trusted.

    -

    +

    If dnssec-lookaside is set to no, then dnssec-lookaside is not used.

    -

    +

    NOTE: The ISC-provided DLV service at dlv.isc.org, has been shut down. The dnssec-lookaside auto; @@ -3464,10 +3270,9 @@ options { up to use ISC DLV with minimal configuration, has accordingly been removed.

    -
    +
    dnssec-must-be-secure
    -
    -

    +

    Specify hierarchies which must be or may not be secure (signed and validated). If yes, then named will only accept answers if @@ -3477,11 +3282,10 @@ options { trusted-keys or managed-keys statement, or dnssec-validation auto must be active. -

    -
    +

    dns64
    -

    +

    This directive instructs named to return mapped IPv4 addresses to AAAA queries when there are no AAAA records. It is intended to be @@ -3489,11 +3293,11 @@ options { dns64 defines one DNS64 prefix. Multiple DNS64 prefixes can be defined.

    -

    +

    Compatible IPv6 prefixes have lengths of 32, 40, 48, 56, 64 and 96 as per RFC 6052.

    -

    +

    Additionally a reverse IP6.ARPA zone will be created for the prefix to provide a mapping from the IP6.ARPA names to the corresponding IN-ADDR.ARPA names using synthesized @@ -3503,20 +3307,20 @@ options { are settable at the view / options level. These are not settable on a per-prefix basis.

    -

    +

    Each dns64 supports an optional clients ACL that determines which clients are affected by this directive. If not defined, it defaults to any;.

    -

    +

    Each dns64 supports an optional mapped ACL that selects which IPv4 addresses are to be mapped in the corresponding A RRset. If not defined it defaults to any;.

    -

    +

    Normally, DNS64 won't apply to a domain name that owns one or more AAAA records; these records will simply be returned. The optional @@ -3527,7 +3331,7 @@ options { name owns. If not defined, exclude defaults to ::ffff:0.0.0.0/96.

    -

    +

    A optional suffix can also be defined to set the bits trailing the mapped IPv4 address bits. By default these bits are @@ -3535,13 +3339,13 @@ options { matching the prefix and mapped IPv4 address must be zero.

    -

    +

    If recursive-only is set to yes the DNS64 synthesis will only happen for recursive queries. The default is no.

    -

    +

    If break-dnssec is set to yes the DNS64 synthesis will happen even if the result, if validated, would @@ -3560,10 +3364,9 @@ options { suffix ::; }; -

    +
    dnssec-loadkeys-interval
    -
    -

    +

    When a zone is configured with auto-dnssec maintain; its key repository must be checked periodically to see if any new keys have been added @@ -3576,11 +3379,10 @@ options { the minimum is 1 (1 minute), and the maximum is 1440 (24 hours); any higher value is silently reduced. -

    -
    +

    dnssec-update-mode
    -

    +

    If this option is set to its default value of maintain in a zone of type master which is DNSSEC-signed @@ -3593,13 +3395,13 @@ options { by regenerating RRSIG records whenever they approach their expiration date.

    -

    +

    If the option is changed to no-resign, then named will sign all new or changed records, but scheduled maintenance of signatures is disabled.

    -

    +

    With either of these settings, named will reject updates to a DNSSEC-signed zone when the signing keys are inactive or unavailable to @@ -3608,15 +3410,15 @@ options { signing and allow DNSSEC data to be submitted into a zone via dynamic update; this is not yet implemented.)

    -
    +
    nta-lifetime
    -

    +

    Species the default lifetime, in seconds, that will be used for negative trust anchors added via rndc nta.

    -

    +

    A negative trust anchor selectively disables DNSSEC validation for zones that are known to be failing because of misconfiguration rather than @@ -3628,21 +3430,21 @@ options { NTA's lifetime is elapsed. NTAs persist across named restarts.

    -

    +

    For convenience, TTL-style time unit suffixes can be used to specify the NTA lifetime in seconds, minutes or hours. nta-lifetime defaults to one hour. It cannot exceed one week.

    -
    +
    nta-recheck
    -

    +

    Species how often to check whether negative trust anchors added via rndc nta are still necessary.

    -

    +

    A negative trust anchor is normally used when a domain has stopped validating due to operator error; it temporarily disables DNSSEC validation for that @@ -3653,23 +3455,23 @@ options { to find out whether it can now be validated. If so, the negative trust anchor is allowed to expire early.

    -

    +

    Validity checks can be disabled for an individual NTA by using rndc nta -f, or for all NTAs by setting nta-recheck to zero.

    -

    +

    For convenience, TTL-style time unit suffixes can be used to specify the NTA recheck interval in seconds, minutes or hours. The default is five minutes. It cannot be longer than nta-lifetime (which cannot be longer than a week).

    -
    +
    max-zone-ttl
    -

    +

    Specifies a maximum permissible TTL value in seconds. For convenience, TTL-style time unit suffixes may be used to specify the maximum value. @@ -3680,7 +3482,7 @@ options { max-zone-ttl will cause the zone to be rejected.

    -

    +

    This is useful in DNSSEC-signed zones because when rolling to a new DNSKEY, the old key needs to remain available until RRSIG records have expired from @@ -3688,46 +3490,46 @@ options { that the largest TTL in the zone will be no higher than the set value.

    -

    +

    (NOTE: Because map-format files load directly into memory, this option cannot be used with them.)

    -

    +

    The default value is unlimited. A max-zone-ttl of zero is treated as unlimited.

    -
    +
    stale-answer-ttl
    -

    +

    Specifies the TTL to be returned on stale answers. The default is 1 second. The minimum allowed is also 1 second; a value of 0 will be updated silently to 1 second.

    -

    +

    For stale answers to be returned, they must be enabled, either in the configuration file using stale-answer-enable or via rndc serve-stale on.

    -
    +
    serial-update-method
    -

    +

    Zones configured for dynamic DNS may use this option to set the update method that will be used for the zone serial number in the SOA record.

    -

    +

    With the default setting of serial-update-method increment;, the SOA serial number will be incremented by one each time the zone is updated.

    -

    +

    When set to serial-update-method unixtime;, the SOA serial number will be set to the number of seconds @@ -3735,7 +3537,7 @@ options { already greater than or equal to that value, in which case it is simply incremented by one.

    -

    +

    When set to serial-update-method date;, the new SOA serial number will be the current date @@ -3744,10 +3546,10 @@ options { than or equal to that value, in which case it is incremented by one.

    -
    +
    zone-statistics
    -

    +

    If full, the server will collect statistical data on all zones (unless specifically turned off on a per-zone basis by specifying @@ -3759,7 +3561,7 @@ options { current serial number, but not query type counters).

    -

    +

    These statistics may be accessed via the statistics-channel or using rndc stats, which @@ -3767,7 +3569,7 @@ options { in the statistics-file. See also the section called “The Statistics File”.

    -

    +

    For backward compatibility with earlier versions of BIND 9, the zone-statistics option can also accept yes @@ -3778,36 +3580,34 @@ options { as none; previously, it was the same as terse.

    -
    +
    - -
    +

    Boolean Options

    - -
    +
    automatic-interface-scan
    -

    +

    If yes and supported by the OS, automatically rescan network interfaces when the interface addresses are added or removed. The default is yes.

    -

    +

    Currently the OS needs to support routing sockets for automatic-interface-scan to be supported.

    -
    +
    allow-new-zones
    -

    +

    If yes, then zones can be added at runtime via rndc addzone. The default is no.

    -

    +

    Newly added zones' configuration parameters are stored so that they can persist after the server is restarted. The configuration information @@ -3821,7 +3621,7 @@ options { incompatible with use as a file name, in which case a cryptographic hash of the view name is used instead.

    -

    +

    Zones added at runtime will have their configuration stored either in a new-zone file (NZF) or a new-zone database (NZD) depending on whether @@ -3830,10 +3630,9 @@ options { See rndc(8) for further details about rndc addzone.

    -
    +
    auth-nxdomain
    -
    -

    +

    If yes, then the AA bit is always set on NXDOMAIN responses, even if the server is not actually @@ -3842,30 +3641,25 @@ options { a change from BIND 8. If you are using very old DNS software, you may need to set it to yes. -

    -
    +

    deallocate-on-exit
    -
    -

    +

    This option was used in BIND 8 to enable checking for memory leaks on exit. BIND 9 ignores the option and always performs the checks. -

    -
    +

    memstatistics
    -
    -

    +

    Write memory statistics to the file specified by memstatistics-file at exit. The default is no unless '-m record' is specified on the command line in which case it is yes. -

    -
    +

    dialup
    -

    +

    If yes, then the server treats all zones as if they are doing zone transfers across @@ -3880,14 +3674,14 @@ options { the normal zone maintenance traffic. The default is no.

    -

    +

    The dialup option may also be specified in the view and zone statements, in which case it overrides the global dialup option.

    -

    +

    If the zone is a master zone, then the server will send out a NOTIFY request to all the slaves (default). This should trigger the @@ -3899,7 +3693,7 @@ options { by notify and also-notify.

    -

    +

    If the zone is a slave or stub zone, then the server will suppress the regular @@ -3909,7 +3703,7 @@ options { addition to sending NOTIFY requests.

    -

    +

    Finer control can be achieved by using notify which only sends NOTIFY messages, @@ -3924,9 +3718,7 @@ options { refresh processing.

    - -
    - +
    @@ -4077,27 +3869,21 @@ options { -
    -
    - -

    +

    +

    Note that normal NOTIFY processing is not affected by dialup.

    - - +
    fake-iquery
    -
    -

    +

    In BIND 8, this option enabled simulating the obsolete DNS query type IQUERY. BIND 9 never does IQUERY simulation. -

    -
    +

    fetch-glue
    -
    -

    +

    This option is obsolete. In BIND 8, fetch-glue yes caused the server to attempt to fetch glue resource records @@ -4106,28 +3892,22 @@ options { data section of a response. This is now considered a bad idea and BIND 9 never does it. -

    -
    +

    flush-zones-on-shutdown
    -
    -

    +

    When the nameserver exits due receiving SIGTERM, flush or do not flush any pending zone writes. The default is flush-zones-on-shutdown no. -

    -
    +

    geoip-use-ecs
    -
    -

    +

    This option was part of an experimental implementation of the EDNS CLIENT-SUBNET for authoritative servers, but is now obsolete. -

    -
    +

    has-old-clients
    -
    -

    +

    This option was incorrectly implemented in BIND 8, and is ignored by BIND 9. To achieve the intended effect @@ -4135,28 +3915,22 @@ options { has-old-clients yes, specify the two separate options auth-nxdomain yes and rfc2308-type1 no instead. -

    -
    +

    host-statistics
    -
    -

    +

    In BIND 8, this enabled keeping of statistics for every host that the name server interacts with. Not implemented in BIND 9. -

    -
    +

    root-key-sentinel
    -
    -

    +

    Respond to root key sentinel probes as described in draft-ietf-dnsop-kskroll-sentinel-08. The default is yes. -

    -
    +

    maintain-ixfr-base
    -
    -

    +

    This option is obsolete. It was used in BIND 8 to determine whether a transaction log was @@ -4164,11 +3938,9 @@ options { log whenever possible. If you need to disable outgoing incremental zone transfers, use provide-ixfr no. -

    -
    +

    message-compression
    -
    -

    +

    If yes, DNS name compression is used in responses to regular queries (not including AXFR or IXFR, which always uses compression). Setting @@ -4178,18 +3950,17 @@ options { to be processed using TCP; a server with compression disabled is out of compliance with RFC 1123 Section 6.1.3.2. The default is yes. -

    -
    +

    minimal-responses
    -

    +

    If set to yes, then when generating responses the server will only add records to the authority and additional data sections when they are required (e.g. delegations, negative responses). This may improve the performance of the server.

    -

    +

    When set to no-auth, the server will omit records from the authority section unless they are required, but it may still add @@ -4204,31 +3975,30 @@ options { designed for mixed-mode servers which handle both authoritative and recursive queries.

    -

    +

    The default is no-auth-recursive.

    -
    +
    glue-cache
    -

    +

    When set to yes, a cache is used to improve query performance when adding address-type (A and AAAA) glue records to the additional section of DNS response messages that delegate to a child zone.

    -

    +

    The glue cache uses memory proportional to the number of delegations in the zone. The default setting is yes, which improves performance at the cost of increased memory usage for the zone. If you don't want this, set it to no.

    -
    +
    minimal-any
    -
    -

    +

    If set to yes, then when generating a positive response to a query of type ANY over UDP, the server will reply with only one @@ -4245,21 +4015,18 @@ options { turned on for these queries, so no unnecessary records will be added to the authority or additional sections. The default is no. -

    -
    +

    multiple-cnames
    -
    -

    +

    This option was used in BIND 8 to allow a domain name to have multiple CNAME records in violation of the DNS standards. BIND 9.2 onwards always strictly enforces the CNAME rules both in master files and dynamic updates. -

    -
    +

    notify
    -

    +

    If yes (the default), DNS NOTIFY messages are sent when a zone the server is authoritative for @@ -4270,7 +4037,7 @@ options { in the SOA MNAME field), and to any servers listed in the also-notify option.

    -

    +

    If master-only, notifies are only sent for master zones. @@ -4279,7 +4046,7 @@ options { servers explicitly listed using also-notify. If no, no notifies are sent.

    -

    +

    The notify option may also be specified in the zone statement, @@ -4288,10 +4055,9 @@ options { caused slaves to crash.

    -
    +
    notify-to-soa
    -
    -

    +

    If yes do not check the nameservers in the NS RRset against the SOA MNAME. Normally a NOTIFY message is not sent to the SOA MNAME (SOA ORIGIN) as it is @@ -4300,11 +4066,9 @@ options { hidden master configurations and in that case you would want the ultimate master to still send NOTIFY messages to all the nameservers listed in the NS RRset. -

    -
    +

    recursion
    -
    -

    +

    If yes, and a DNS query requests recursion, then the server will attempt to do @@ -4320,11 +4084,9 @@ options { queries. Caching may still occur as an effect the server's internal operation, such as NOTIFY address lookups. -

    -
    +

    request-nsid
    -
    -

    +

    If yes, then an empty EDNS(0) NSID (Name Server Identifier) option is sent with all queries to authoritative name servers during iterative @@ -4333,26 +4095,21 @@ options { the nsid category at level info. The default is no. -

    -
    +

    request-sit
    -
    -

    +

    This experimental option is obsolete. -

    -
    +

    require-server-cookie
    -
    -

    +

    Require a valid server cookie before sending a full response to a UDP request from a cookie aware client. BADCOOKIE is sent if there is a bad or no existent server cookie. -

    -
    +

    answer-cookie
    -

    +

    When set to the default value of yes, COOKIE EDNS options will be sent when applicable in replies to client queries. If set to @@ -4360,7 +4117,7 @@ options { be sent in replies. This can only be set at the global options level, not per-view.

    -

    +

    answer-cookie no is intended as a temporary measure, for use when named shares an IP address with other servers that do not yet @@ -4371,10 +4128,9 @@ options { caution. DNS COOKIE is an important security mechanism, and should not be disabled unless absolutely necessary.

    -
    +
    send-cookie
    -
    -

    +

    If yes, then a COOKIE EDNS option is sent along with the query. If the resolver has previously talked to the server, the @@ -4390,16 +4146,15 @@ options { do not send a correct COOKIE option may be limited to receiving smaller responses via the nocookie-udp-size option. -

    -
    +

    stale-answer-enable
    -

    +

    Enable the returning of "stale" cached answers when the nameservers for a zone are not answering. The default is not to return stale answers.

    -

    +

    Stale answers can also be enabled or disabled at runtime via rndc serve-stale on or rndc serve-stale off; these @@ -4414,39 +4169,33 @@ options { rndc serve-stale on, or the server must be restarted.

    -

    +

    Information about stale answers is logged under the serve-stale log category.

    -
    +
    nocookie-udp-size
    -
    -

    +

    Sets the maximum size of UDP responses that will be sent to queries without a valid server COOKIE. A value below 128 will be silently raised to 128. The default value is 4096, but the max-udp-size option may further limit the response size. -

    -
    +

    sit-secret
    -
    -

    +

    This experimental option is obsolete. -

    -
    +

    cookie-algorithm
    -
    -

    +

    Set the algorithm to be used when generating the server cookie. One of "aes", "sha1" or "sha256". The default is "aes" if supported by the cryptographic library or otherwise "sha256". -

    -
    +

    cookie-secret
    -

    +

    If set, this is a shared secret used for generating and verifying EDNS COOKIE options within an anycast cluster. If not set, the system @@ -4455,16 +4204,16 @@ options { to be 128 bits for AES128, 160 bits for SHA1 and 256 bits for SHA256.

    -

    +

    If there are multiple secrets specified, the first one listed in named.conf is used to generate new server cookies. The others will only be used to verify returned cookies.

    -
    +
    response-padding
    -

    +

    The EDNS Padding option is intended to improve confidentiality when DNS queries are sent over an encrypted channel by reducing the variability in @@ -4491,7 +4240,7 @@ options { If these conditions are not met, the response is not padded.

    -

    +

    If block-size is 0 or the ACL is none;, then this feature is disabled and no padding will occur; this is the @@ -4500,33 +4249,33 @@ options { to 512. Block sizes are ordinarily expected to be powers of two (for instance, 128), but this is not mandatory.

    -
    +
    rfc2308-type1
    -

    +

    Setting this to yes will cause the server to send NS records along with the SOA record for negative answers. The default is no.

    -
    +

    Note

    -

    +

    Not yet implemented in BIND 9.

    -
    -
    +
    +
    trust-anchor-telemetry
    -

    +

    Causes named to send specially-formed queries once per day to domains for which trust anchors have been configured via trusted-keys, managed-keys, or dnssec-validation auto.

    -

    +

    The query name used for these queries has the form "_ta-xxxx(-xxxx)(...)".<domain>, where each "xxxx" is a group of four hexadecimal digits @@ -4534,27 +4283,24 @@ options { The key IDs for each domain are sorted smallest to largest prior to encoding. The query type is NULL.

    -

    +

    By monitoring these queries, zone operators will be able to see which resolvers have been updated to trust a new key; this may help them decide when it is safe to remove an old one.

    -

    +

    The default is yes.

    -
    +
    use-id-pool
    -
    -

    +

    This option is obsolete. BIND 9 always allocates query IDs from a pool. -

    -
    +

    use-ixfr
    -
    -

    +

    This option is obsolete. If you need to disable IXFR to a particular server or servers, see @@ -4563,38 +4309,30 @@ options { Usage”. See also the section called “Incremental Zone Transfers (IXFR)”. -

    -
    +

    provide-ixfr
    -
    -

    +

    See the description of provide-ixfr in the section called “server Statement Definition and Usage”. -

    -
    +

    request-ixfr
    -
    -

    +

    See the description of request-ixfr in the section called “server Statement Definition and Usage”. -

    -
    +

    request-expire
    -
    -

    +

    See the description of request-expire in the section called “server Statement Definition and Usage”. -

    -
    +

    treat-cr-as-space
    -
    -

    +

    This option was used in BIND 8 to make the server treat carriage return ("\r") characters the same way @@ -4605,16 +4343,15 @@ options { and NT/DOS "\r\n" newlines are always accepted, and the option is ignored. -

    -
    +

    match-mapped-addresses
    -

    +

    If yes, then an IPv4-mapped IPv6 address will match any address match list entries that match the corresponding IPv4 address.

    -

    +

    This option was introduced to work around a kernel quirk in some operating systems that causes IPv4 TCP connections, such as zone transfers, to be accepted on an @@ -4623,10 +4360,10 @@ options { named now solves this problem internally. The use of this option is discouraged.

    -
    +
    filter-aaaa-on-v4
    -

    +

    This option is intended to help the transition from IPv4 to IPv6 by not giving IPv6 addresses to DNS clients unless they have connections to the IPv6 @@ -4637,7 +4374,7 @@ options { to override the global filter-aaaa-on-v4 option.

    -

    +

    If yes, the DNS client is at an IPv4 address, in filter-aaaa, and if the response does not include DNSSEC signatures, @@ -4645,13 +4382,13 @@ options { This filtering applies to all responses and not only authoritative responses.

    -

    +

    If break-dnssec, then AAAA records are deleted even when DNSSEC is enabled. As suggested by the name, this makes the response not verify, because the DNSSEC protocol is designed detect deletions.

    -

    +

    This mechanism can erroneously cause other servers to not give AAAA records to their clients. A recursing server with both IPv6 and IPv4 network connections @@ -4659,31 +4396,29 @@ options { via IPv4 will be denied AAAA records even if its client is using IPv6.

    -

    +

    This mechanism is applied to authoritative as well as non-authoritative records. A client using IPv4 that is not allowed recursion can erroneously be given AAAA records because the server is not allowed to check for A records.

    -

    +

    Some AAAA records are given to IPv4 clients in glue records. IPv4 clients that are servers can then erroneously answer requests for AAAA records received via IPv4.

    -
    +
    filter-aaaa-on-v6
    -
    -

    +

    Identical to filter-aaaa-on-v4, except it filters AAAA responses to queries from IPv6 clients instead of IPv4 clients. To filter all responses, set both options to yes. -

    -
    +

    ixfr-from-differences
    -

    +

    When yes and the server loads a new version of a master zone from its zone file or receives a new version of a slave file via zone transfer, it will @@ -4693,7 +4428,7 @@ options { transmitted to downstream slaves as an incremental zone transfer.

    -

    +

    By allowing incremental zone transfers to be used for non-dynamic zones, this option saves bandwidth at the expense of increased CPU and memory consumption at the @@ -4705,7 +4440,7 @@ options { temporarily allocate memory to hold this complete difference set.

    -

    ixfr-from-differences +

    ixfr-from-differences also accepts master (or primary) and slave (or secondary) @@ -4714,10 +4449,14 @@ options { all primary or secondary zones, respectively. It is off for all zones by default.

    -
    +

    + Note: if inline signing is enabled for a zone, the + user-provided ixfr-from-differences + setting is ignored for that zone. +

    +
    multi-master
    -
    -

    +

    This should be set when you have multiple masters for a zone and the addresses refer to different machines. If yes, named will @@ -4725,22 +4464,21 @@ options { when the serial number on the master is less than what named currently has. The default is no. -

    -
    +

    auto-dnssec
    -

    +

    Zones configured for dynamic DNS may use this option to allow varying levels of automatic DNSSEC key management. There are three possible settings:

    -

    +

    auto-dnssec allow; permits keys to be updated and the zone fully re-signed whenever the user issues the command rndc sign zonename.

    -

    +

    auto-dnssec maintain; includes the above, but also automatically adjusts the zone's DNSSEC keys on schedule, according to the keys' timing metadata @@ -4763,31 +4501,29 @@ options { interval is defined by dnssec-loadkeys-interval.)

    -

    +

    The default setting is auto-dnssec off.

    -
    +
    dnssec-enable
    -
    -

    +

    This indicates whether DNSSEC-related resource records are to be returned by named. If set to no, named will not return DNSSEC-related resource records unless specifically queried for. The default is yes. -

    -
    +

    dnssec-validation
    -

    +

    Enable DNSSEC validation in named. Note dnssec-enable also needs to be set to yes to be effective. If set to no, DNSSEC validation is disabled.

    -

    +

    If set to auto, DNSSEC validation is enabled, and a default trust anchor for the DNS root zone is used. If set to yes, @@ -4796,7 +4532,7 @@ options { or managed-keys statement. The default is yes.

    -

    +

    The default root trust anchor is stored in the file bind.keys. named will load that key at @@ -4807,16 +4543,16 @@ options { bind.keys can be downloaded from https://www.isc.org/bind-keys.

    -

    +

    To prevent problems if bind.keys is not found, the current trust anchor is also compiled in to named. Relying on this is not recommended, however, as it requires named to be recompiled with a new key when the root key expires.)

    -
    +

    Note

    -

    +

    named only loads the root key from bind.keys. The file cannot be used to store keys for other zones. @@ -4824,37 +4560,46 @@ options { if dnssec-validation auto is not in use.

    -

    +

    Whenever the resolver sends out queries to an EDNS-compliant server, it always sets the DO bit indicating it can support DNSSEC responses even if dnssec-validation is off.

    -
    -
    +
    + +
    validate-except
    +

    + Specifies a list of domain names at and beneath which DNSSEC + validation should not be performed, + regardless of the presence of a trust anchor at or above + those names. This may be used, for example, when configuring + a top-level domain intended only for local use, so that the + lack of a secure delegation for that domain in the root zone + will not cause validation failures. (This is similar + to setting a negative trust anchor, except that it is a + permanent configuration, whereas negative trust anchors + expire and are removed after a set period of time.) +

    dnssec-accept-expired
    -
    -

    +

    Accept expired signatures when verifying DNSSEC signatures. The default is no. Setting this option to yes leaves named vulnerable to replay attacks. -

    -
    +

    querylog
    -
    -

    +

    Specify whether query logging should be started when named starts. If querylog is not specified, then the query logging is determined by the presence of the logging category queries. -

    -
    +

    check-names
    -

    +

    This option is used to restrict the character set and syntax of certain domain names in master files and/or DNS responses @@ -4867,11 +4612,11 @@ options { For answers received from the network (response) the default is ignore.

    -

    +

    The rules for legal hostnames and mail domains are derived from RFC 952 and RFC 821 as modified by RFC 1123.

    -

    check-names +

    check-names applies to the owner names of A, AAAA and MX records. It also applies to the domain names in the RDATA of NS, SOA, MX, and SRV records. @@ -4879,29 +4624,24 @@ options { name indicated that it is a reverse lookup of a hostname (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).

    -
    +
    check-dup-records
    -
    -

    +

    Check master zones for records that are treated as different by DNSSEC but are semantically equal in plain DNS. The default is to warn. Other possible values are fail and ignore. -

    -
    +

    check-mx
    -
    -

    +

    Check whether the MX record appears to refer to a IP address. The default is to warn. Other possible values are fail and ignore. -

    -
    +

    check-wildcard
    -
    -

    +

    This option is used to check for non-terminal wildcards. The use of non-terminal wildcards is almost always as a result of a failure @@ -4909,11 +4649,10 @@ options { This option affects master zones. The default (yes) is to check for non-terminal wildcards and issue a warning. -

    -
    +

    check-integrity
    -

    +

    Perform post load zone integrity checks on master zones. This checks that MX and SRV records refer to address (A or AAAA) records and that glue @@ -4926,7 +4665,7 @@ options { checks use named-checkzone). The default is yes.

    -

    +

    The use of the SPF record for publishing Sender Policy Framework is deprecated as the migration from using TXT records to SPF records was abandoned. @@ -4936,65 +4675,53 @@ options { TXT record does not exist and can be suppressed with check-spf.

    -
    +
    check-mx-cname
    -
    -

    +

    If check-integrity is set then fail, warn or ignore MX records that refer to CNAMES. The default is to warn. -

    -
    +

    check-srv-cname
    -
    -

    +

    If check-integrity is set then fail, warn or ignore SRV records that refer to CNAMES. The default is to warn. -

    -
    +

    check-sibling
    -
    -

    +

    When performing integrity checks, also check that sibling glue exists. The default is yes. -

    -
    +

    check-spf
    -
    -

    +

    If check-integrity is set then check that there is a TXT Sender Policy Framework record present (starts with "v=spf1") if there is an SPF record present. The default is warn. -

    -
    +

    zero-no-soa-ttl
    -
    -

    +

    When returning authoritative negative responses to SOA queries set the TTL of the SOA record returned in the authority section to zero. The default is yes. -

    -
    +

    zero-no-soa-ttl-cache
    -
    -

    +

    When caching a negative response to a SOA query set the TTL to zero. The default is no. -

    -
    +

    update-check-ksk
    -

    +

    When set to the default value of yes, check the KSK bit in each key to determine how the key should be used when generating RRSIGs for a secure zone.

    -

    +

    Ordinarily, zone-signing keys (that is, keys without the KSK bit set) are used to sign the entire zone, while key-signing keys (keys with the KSK bit set) are only @@ -5005,7 +4732,7 @@ options { similar to the dnssec-signzone -z command line option.

    -

    +

    When this option is set to yes, there must be at least two active keys for every algorithm represented in the DNSKEY RRset: at least one KSK and one @@ -5013,10 +4740,10 @@ options { this requirement is not met, this option will be ignored for that algorithm.

    -
    +
    dnssec-dnskey-kskonly
    -

    +

    When this option and update-check-ksk are both set to yes, only key-signing keys (that is, keys with the KSK bit set) will be used @@ -5026,23 +4753,21 @@ options { This is similar to the dnssec-signzone -x command line option.

    -

    +

    The default is no. If update-check-ksk is set to no, this option is ignored.

    -
    +
    try-tcp-refresh
    -
    -

    +

    Try to refresh the zone using TCP if UDP queries fail. For BIND 8 compatibility, the default is yes. -

    -
    +

    dnssec-secure-to-insecure
    -

    +

    Allow a dynamic zone to transition from secure to insecure (i.e., signed to unsigned) by deleting all of the DNSKEY records. The default is no. @@ -5050,55 +4775,52 @@ options { at the zone apex is deleted, all RRSIG and NSEC records will be removed from the zone as well.

    -

    +

    If the zone uses NSEC3, then it is also necessary to delete the NSEC3PARAM RRset from the zone apex; this will cause the removal of all corresponding NSEC3 records. (It is expected that this requirement will be eliminated in a future release.)

    -

    +

    Note that if a zone has been configured with auto-dnssec maintain and the private keys remain accessible in the key repository, then the zone will be automatically signed again the next time named is started.

    -
    +
    synth-from-dnssec
    -

    +

    Synthesize answers from cached NSEC, NSEC3 and other RRsets that have been proved to be correct using DNSSEC. The default is yes.

    -

    +

    Note:

    • -

      +

      DNSSEC validation must be enabled for this option to be effective.

      -

      +

      This initial implementation only covers synthesis of answers from NSEC records. Synthesis from NSEC3 is planned for the future. This will also be controlled by synth-from-dnssec.

      -
    +

- +
- -
- -
+
+

Forwarding

- -

+

The forwarding facility can be used to create a large site-wide cache on a few servers, reducing traffic over links to external name servers. It can also be used to allow queries by servers that @@ -5108,11 +4830,9 @@ options { the server is not authoritative and does not have the answer in its cache.

- -
+
forward
-
-

+

This option is only meaningful if the forwarders list is not empty. A value of first, the default, causes the server to query the forwarders @@ -5122,19 +4842,15 @@ options { the answer itself. If only is specified, the server will only query the forwarders. -

-
+

forwarders
-
-

+

Specifies the IP addresses to be used for forwarding. The default is the empty list (no forwarding). -

-
+

- -

+

Forwarding can also be configured on a per-domain basis, allowing for the global forwarding options to be overridden in a variety of ways. You can set particular domains to use different @@ -5143,24 +4859,20 @@ options { or not forward at all, see the section called “zone Statement Grammar”.

-
- -
+
+

Dual-stack Servers

- -

+

Dual-stack servers are used as servers of last resort to work around problems in reachability due the lack of support for either IPv4 or IPv6 on the host machine.

- -
+
dual-stack-servers
-
-

+

Specifies host names or addresses of machines with access to both IPv4 and IPv6 transports. If a hostname is used, the server must be able @@ -5169,26 +4881,20 @@ options { stacked, then the dual-stack-servers have no effect unless access to a transport has been disabled on the command line (e.g. named -4). -

-
+

-
- -
+
+

Access Control

- - -

+

Access to the server can be restricted based on the IP address of the requesting system. See the section called “Address Match Lists” for details on how to specify IP address lists.

- -
+
allow-notify
-
-

+

Specifies which hosts are allowed to notify this server, a slave, of zone changes in addition to the zone masters. @@ -5201,11 +4907,10 @@ options { for a slave zone. If not specified, the default is to process notify messages only from a zone's master. -

-
+

allow-query
-

+

Specifies which hosts are allowed to ask ordinary DNS questions. allow-query may also be specified in the zone @@ -5214,50 +4919,49 @@ options { If not specified, the default is to allow queries from all hosts.

-
+

Note

-

+

allow-query-cache is now used to specify access to the cache.

-
-
+
+
allow-query-on
-

+

Specifies which local addresses can accept ordinary DNS questions. This makes it possible, for instance, to allow queries on internal-facing interfaces but disallow them on external-facing ones, without necessarily knowing the internal network's addresses.

-

+

Note that allow-query-on is only checked for queries that are permitted by allow-query. A query must be allowed by both ACLs, or it will be refused.

-

+

allow-query-on may also be specified in the zone statement, in which case it overrides the options allow-query-on statement.

-

+

If not specified, the default is to allow queries on all addresses.

-
+

Note

-

+

allow-query-cache is used to specify access to the cache.

-
-
+
+
allow-query-cache
-
-

+

Specifies which hosts are allowed to get answers from the cache. If allow-query-cache is not set then allow-recursion @@ -5266,21 +4970,17 @@ options { set in which case none; is used, otherwise the default (localnets; localhost;) is used. -

-
+

allow-query-cache-on
-
-

+

Specifies which local addresses can give answers from the cache. If not specified, the default is to allow cache queries on any address, localnets and localhost. -

-
+

allow-recursion
-
-

+

Specifies which hosts are allowed to make recursive queries through this server. If allow-recursion is not set @@ -5289,30 +4989,25 @@ options { is used if set, otherwise the default (localnets; localhost;) is used. -

-
+

allow-recursion-on
-
-

+

Specifies which local addresses can accept recursive queries. If not specified, the default is to allow recursive queries on all addresses. -

-
+

allow-update
-
-

+

Specifies which hosts are allowed to submit Dynamic DNS updates for master zones. The default is to deny updates from all hosts. Note that allowing updates based on the requestor's IP address is insecure; see the section called “Dynamic Update Security” for details. -

-
+

allow-update-forwarding
-

+

Specifies which hosts are allowed to submit Dynamic DNS updates to slave zones to be forwarded to the @@ -5329,7 +5024,7 @@ options { with the master server, not the slaves.

-

+

Note that enabling the update forwarding feature on a slave server may expose master servers relying on insecure IP address @@ -5337,10 +5032,9 @@ options { access control to attacks; see the section called “Dynamic Update Security” for more details.

-
+
allow-v6-synthesis
-
-

+

This option was introduced for the smooth transition from AAAA to A6 and from "nibble labels" to binary labels. @@ -5348,11 +5042,9 @@ options { deprecated, this option was also deprecated. It is now ignored with some warning messages. -

-
+

allow-transfer
-
-

+

Specifies which hosts are allowed to receive zone transfers from the server. allow-transfer may also be specified in the zone @@ -5360,40 +5052,33 @@ options { case it overrides the options allow-transfer statement. If not specified, the default is to allow transfers to all hosts. -

-
+

blackhole
-
-

+

Specifies a list of addresses that the server will not accept queries from or use to resolve a query. Queries from these addresses will not be responded to. The default is none. -

-
+

filter-aaaa
-
-

+

Specifies a list of addresses to which filter-aaaa-on-v4 and filter-aaaa-on-v6 apply. The default is any. -

-
+

keep-response-order
-
-

+

Specifies a list of addresses to which the server will send responses to TCP queries in the same order in which they were received. This disables the processing of TCP queries in parallel. The default is none. -

-
+

no-case-compress
-

+

Specifies a list of addresses which require responses to use case-insensitive compression. This ACL can be used when named needs to work with @@ -5401,7 +5086,7 @@ options { 1034 to use case-insensitive name comparisons when checking for matching domain names.

-

+

If left undefined, the ACL defaults to none: case-insensitive compression will be used for all clients. If the ACL is defined and @@ -5409,7 +5094,7 @@ options { compressing domain names in DNS responses sent to that client.

-

+

This can result in slightly smaller responses: if a response contains the names "example.com" and "example.COM", case-insensitive compression would treat @@ -5421,12 +5106,12 @@ options { match the query, which is required by some clients due to incorrect use of case-sensitive comparisons.

-

+

Case-insensitive compression is always used in AXFR and IXFR responses, regardless of whether the client matches this ACL.

-

+

There are circumstances in which named will not preserve the case of owner names of records: if a zone file defines records of different types with @@ -5441,10 +5126,10 @@ options { have their case preserved unless the client matches this ACL.

-
+
resolver-query-timeout
-

+

The amount of time in milliseconds that the resolver will spend attempting to resolve a recursive query before failing. The default and minimum @@ -5453,22 +5138,19 @@ options { 0 will result in the default being used.

-

+

This value was originally specified in seconds. Values less than or equal to 300 will be be treated as seconds and converted to milliseconds before applying the above limits.

-
+
- -
- -
+
+

Interfaces

- -

+

The interfaces and ports that the server will answer queries from may be specified using the listen-on option. listen-on takes an optional port and an address_match_list @@ -5477,35 +5159,30 @@ options { The server will listen on all interfaces allowed by the address match list. If a port is not specified, port 53 will be used.

-

+

Multiple listen-on statements are allowed. For example,

- 
listen-on { 5.6.7.8; };
 listen-on port 1234 { !1.2.3.4; 1.2/16; };
- -

+

will enable the name server on port 53 for the IP address 5.6.7.8, and on port 1234 of an address on the machine in net 1.2 that is not 1.2.3.4.

- -

+

If no listen-on is specified, the server will listen on port 53 on all IPv4 interfaces.

- -

+

The listen-on-v6 option is used to specify the interfaces and the ports on which the server will listen for incoming queries sent using IPv6. If not specified, the server will listen on port 53 on all IPv6 interfaces.

- -

+

When 

{ any; }

is @@ -5520,8 +5197,7 @@ listen-on port 1234 { !1.2.3.4; 1.2/16; }; If the system only has incomplete API support for IPv6, however, the behavior is the same as that for IPv4.

- -

+

A list of particular IPv6 addresses can also be specified, in which case the server listens on a separate socket for each specified @@ -5530,38 +5206,30 @@ listen-on port 1234 { !1.2.3.4; 1.2/16; }; IPv4 addresses specified in listen-on-v6 will be ignored, with a logged warning.

- -

+

Multiple listen-on-v6 options can be used. For example,

- 
listen-on-v6 { any; };
 listen-on-v6 port 1234 { !2001:db8::/32; any; };
- -

+

will enable the name server on port 53 for any IPv6 addresses (with a single wildcard socket), and on port 1234 of IPv6 addresses that is not in the prefix 2001:db8::/32 (with separate sockets for each matched address.)

- -

+

To make the server not listen on any IPv6 address, use

- 
listen-on-v6 { none; };
- -
- -
+
+

Query Address

- -

+

If the server doesn't know the answer to a question, it will query other name servers. query-source specifies the address and port used for such queries. For queries sent over @@ -5570,8 +5238,7 @@ listen-on-v6 port 1234 { !2001:db8::/32; any; }; a wildcard IP address (INADDR_ANY) will be used.

- -

+

If port is * or is omitted, a random port number from a pre-configured range is picked up and will be used for each query. @@ -5582,18 +5249,15 @@ listen-on-v6 port 1234 { !2001:db8::/32; any; }; the avoid-v4-udp-ports and avoid-v6-udp-ports options, respectively.

- -

+

The defaults of the query-source and query-source-v6 options are:

- 
query-source address * port *;
 query-source-v6 address * port *;
- -

+

If use-v4-udp-ports or use-v6-udp-ports is unspecified, named will check if the operating @@ -5603,12 +5267,10 @@ query-source-v6 address * port *; named will use the corresponding system default range; otherwise, it will use its own defaults:

- 
use-v4-udp-ports { range 1024 65535; };
 use-v6-udp-ports { range 1024 65535; };
- -

+

Note: make sure the ranges be sufficiently large for security. A desirable size depends on various parameters, but we generally recommend it contain at least 16384 ports @@ -5624,8 +5286,7 @@ use-v6-udp-ports { range 1024 65535; }; ranges are sufficiently large and are reasonably independent from the ranges used by other applications.

- -

+

Note: the operational configuration where named runs may prohibit the use of some ports. For example, UNIX systems will not allow @@ -5637,18 +5298,15 @@ use-v6-udp-ports { range 1024 65535; }; It is therefore important to configure the set of ports that can be safely used in the expected operational environment.

- -

+

The defaults of the avoid-v4-udp-ports and avoid-v6-udp-ports options are:

- 
avoid-v4-udp-ports {};
 avoid-v6-udp-ports {};
- -

+

Note: BIND 9.5.0 introduced the use-queryport-pool option to support a pool of such random ports, but this @@ -5660,67 +5318,57 @@ avoid-v6-udp-ports {}; query-source-v6 options; it implicitly disables the use of randomized port numbers.

- -
+
use-queryport-pool
-
-

+

This option is obsolete. -

-
+

queryport-pool-ports
-
-

+

This option is obsolete. -

-
+

queryport-pool-updateinterval
-
-

+

This option is obsolete. -

-
+

-
+

Note

-

+

The address specified in the query-source option is used for both UDP and TCP queries, but the port applies only to UDP queries. TCP queries always use a random unprivileged port.

-
-
+
+

Note

-

+

Solaris 2.5.1 and earlier does not support setting the source address for TCP sockets.

-
-
+
+

Note

-

+

See also transfer-source and notify-source.

-
-
- -
+
+
+

Zone Transfers

- -

+

BIND has mechanisms in place to facilitate zone transfers and set limits on the amount of load that transfers place on the system. The following options apply to zone transfers.

- -
+
also-notify
-

+

Defines a global list of IP addresses of name servers that are also sent NOTIFY messages whenever a fresh copy of the @@ -5738,7 +5386,7 @@ avoid-v6-udp-ports {}; In place of explicit addresses, one or more named masters lists can be used.

-

+

If an also-notify list is given in a zone statement, it will override @@ -5751,46 +5399,37 @@ avoid-v6-udp-ports {}; the empty list (no global notification list).

-
+
max-transfer-time-in
-
-

+

Inbound zone transfers running longer than this many minutes will be terminated. The default is 120 minutes (2 hours). The maximum value is 28 days (40320 minutes). -

-
+

max-transfer-idle-in
-
-

+

Inbound zone transfers making no progress in this many minutes will be terminated. The default is 60 minutes (1 hour). The maximum value is 28 days (40320 minutes). -

-
+

max-transfer-time-out
-
-

+

Outbound zone transfers running longer than this many minutes will be terminated. The default is 120 minutes (2 hours). The maximum value is 28 days (40320 minutes). -

-
+

max-transfer-idle-out
-
-

+

Outbound zone transfers making no progress in this many minutes will be terminated. The default is 60 minutes (1 hour). The maximum value is 28 days (40320 minutes). -

-
+

notify-rate
-
-

+

The rate at which NOTIFY requests will be sent during normal zone maintenance operations. (NOTIFY requests due to initial zone loading are subject @@ -5798,22 +5437,18 @@ avoid-v6-udp-ports {}; 20 per second. The lowest possible rate is one per second; when set to zero, it will be silently raised to one. -

-
+

startup-notify-rate
-
-

+

The rate at which NOTIFY requests will be sent when the name server is first starting up, or when zones have been newly added to the nameserver. The default is 20 per second. The lowest possible rate is one per second; when set to zero, it will be silently raised to one. -

-
+

serial-query-rate
-
-

+

Slave servers will periodically query master servers to find out if zone serial numbers have changed. Each such query uses a minute amount of @@ -5825,11 +5460,9 @@ avoid-v6-udp-ports {}; per second. The default is 20 per second. The lowest possible rate is one per second; when set to zero, it will be silently raised to one. -

-
+

serial-queries
-
-

+

In BIND 8, the serial-queries option set the maximum number of concurrent serial number queries @@ -5838,12 +5471,9 @@ avoid-v6-udp-ports {}; serial queries and ignores the serial-queries option. Instead, it limits the rate at which the queries are sent as defined using the serial-query-rate option. -

-
+

transfer-format
-
- -

+

Zone transfers can be sent using two different formats, one-answer and many-answers. @@ -5863,12 +5493,10 @@ avoid-v6-udp-ports {}; transfer-format may be overridden on a per-server basis by using the server statement. -

- -
+

transfer-message-size
-

+

This is an upper bound on the uncompressed size of DNS messages used in zone transfers over TCP. If a message grows larger than this size, additional messages will be @@ -5878,7 +5506,7 @@ avoid-v6-udp-ports {}; fit within the size limit, a larger message will be permitted so the record can be transferred.)

-

+

Valid values are between 512 and 65535 octets, and any values outside that range will be adjusted to the nearest value within it. The default is 20480, @@ -5888,35 +5516,30 @@ avoid-v6-udp-ports {}; as effectively, because 16536 is the largest permissible compression offset pointer in a DNS message.

-

+

This option is mainly intended for server testing; there is rarely any benefit in setting a value other than the default.

-
+
transfers-in
-
-

+

The maximum number of inbound zone transfers that can be running concurrently. The default value is 10. Increasing transfers-in may speed up the convergence of slave zones, but it also may increase the load on the local system. -

-
+

transfers-out
-
-

+

The maximum number of outbound zone transfers that can be running concurrently. Zone transfer requests in excess of the limit will be refused. The default value is 10. -

-
+

transfers-per-ns
-
-

+

The maximum number of inbound zone transfers that can be concurrently transferring from a given remote name server. @@ -5928,11 +5551,10 @@ avoid-v6-udp-ports {}; the load on the remote name server. transfers-per-ns may be overridden on a per-server basis by using the transfers phrase of the server statement. -

-
+

transfer-source
-

transfer-source +

transfer-source determines which local address will be bound to IPv4 TCP connections used to fetch zones transferred inbound by the server. It also determines the @@ -5953,30 +5575,28 @@ avoid-v6-udp-ports {}; zone block in the configuration file.

-
+

Note

-

+

Solaris 2.5.1 and earlier does not support setting the source address for TCP sockets.

-
-
+
+
transfer-source-v6
-
-

+

The same as transfer-source, except zone transfers are performed using IPv6. -

-
+

alt-transfer-source
-

+

An alternate transfer source if the one listed in transfer-source fails and use-alt-transfer-source is set.

-
+

Note

If you do not wish the alternate transfer source @@ -5987,29 +5607,25 @@ avoid-v6-udp-ports {}; query.

-
+
alt-transfer-source-v6
-
-

+

An alternate transfer source if the one listed in transfer-source-v6 fails and use-alt-transfer-source is set. -

-
+

use-alt-transfer-source
-
-

+

Use the alternate transfer sources or not. If views are specified this defaults to no otherwise it defaults to yes (for BIND 8 compatibility). -

-
+

notify-source
-

notify-source +

notify-source determines which local source address, and optionally UDP port, will be used to send NOTIFY messages. This address must appear in the slave @@ -6023,30 +5639,25 @@ avoid-v6-udp-ports {}; view block in the configuration file.

-
+

Note

-

+

Solaris 2.5.1 and earlier does not support setting the source address for TCP sockets.

-
-
+
+
notify-source-v6
-
-

+

Like notify-source, but applies to notify messages sent to IPv6 addresses. -

-
+

- -
- -
+
+

UDP Port Lists

- -

+

use-v4-udp-ports, avoid-v4-udp-ports, use-v6-udp-ports, and @@ -6057,20 +5668,17 @@ avoid-v6-udp-ports {}; available ports are determined. For example, with the following configuration

- 
 use-v6-udp-ports { range 32768 65535; };
 avoid-v6-udp-ports { 40000; range 50000 60000; };
- -

+

UDP ports of IPv6 messages sent from named will be in one of the following ranges: 32768 to 39999, 40001 to 49999, and 60001 to 65535.

- -

+

avoid-v4-udp-ports and avoid-v6-udp-ports can be used to prevent named from choosing as its random source port a @@ -6087,13 +5695,11 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; sense; they are provided for backward compatibility and to possibly simplify the port specification.

-
- -
+
+

Operating System Resource Limits

- -

+

The server's usage of many system resources can be limited. Scaled values are allowed when specifying resource limits. For example, 1G can be used instead of @@ -6106,8 +5712,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; that was in force when the server was started. See the description of size_spec in the section called “Configuration File Elements”.

- -

+

The following options set operating system resource limits for the name server process. Some operating systems don't support some or @@ -6115,18 +5720,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; the unsupported limit is used.

- -
+
coresize
-
-

+

The maximum size of a core dump. The default is default. -

-
+

datasize
-
-

+

The maximum amount of data memory the server may use. The default is default. This is a hard limit on server memory usage. @@ -6141,49 +5742,38 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; max-cache-size and recursive-clients options instead. -

-
+

files
-
-

+

The maximum number of files the server may have open concurrently. The default is unlimited. -

-
+

stacksize
-
-

+

The maximum amount of stack memory the server may use. The default is default. -

-
+

- -
- -
+
+

Server Resource Limits

- -

+

The following options set limits on the server's resource consumption that are enforced internally by the server rather than the operating system.

- -
+
max-ixfr-log-size
-
-

+

This option is obsolete; it is accepted and ignored for BIND 8 compatibility. The option max-journal-size performs a similar function in BIND 9. -

-
+

max-journal-size
-

+

Sets a maximum size for each journal file (see the section called “The journal file”), expressed in bytes or, if followed by an optional unit suffix ('k', @@ -6200,28 +5790,24 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; the zone. (There is little benefit in storing larger journals.)

-

+

This option may also be set on a per-zone basis.

-
+
max-records
-
-

+

The maximum number of records permitted in a zone. The default is zero which means unlimited. -

-
+

host-statistics-max
-
-

+

In BIND 8, specifies the maximum number of host statistics entries to be kept. Not implemented in BIND 9. -

-
+

recursive-clients
-

+

The maximum number ("hard quota") of simultaneous recursive lookups the server will perform on behalf of clients. The default is @@ -6232,14 +5818,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; recursive-clients option may have to be decreased on hosts with limited memory.

-

+

recursive-clients defines a "hard quota" limit for pending recursive clients: when more clients than this are pending, new incoming requests will not be accepted, and for each incoming request a previous pending request will also be dropped.

-

+

A "soft quota" is also set. When this lower quota is exceeded, incoming requests are accepted, but for each one, a pending request will be dropped. @@ -6249,20 +5835,18 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; otherwise it is set to 90% of recursive-clients.

-
+
tcp-clients
-
-

+

The maximum number of simultaneous client TCP connections that the server will accept. The default is 150. -

-
+

clients-per-query, max-clients-per-query
-

These set the +

These set the initial value (minimum) and maximum number of recursive simultaneous clients for any given query (<qname,qtype,qclass>) that the server will accept @@ -6270,7 +5854,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; self tune this value and changes will be logged. The default values are 10 and 100.

-

+

This value should reflect how many queries come in for a given name in the time it takes to resolve that name. If the number of queries exceed this value, named will @@ -6280,22 +5864,22 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; estimate will then be lowered in 20 minutes if it has remained unchanged.

-

+

If clients-per-query is set to zero, then there is no limit on the number of clients per query and no queries will be dropped.

-

+

If max-clients-per-query is set to zero, then there is no upper bound other than imposed by recursive-clients.

-
+
fetches-per-zone
-

+

The maximum number of simultaneous iterative queries to any one domain that the server will permit before blocking new queries for data @@ -6305,7 +5889,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; would take to resolve them. It should be smaller than recursive-clients.

-

+

When many clients simultaneously query for the same name and type, the clients will all be attached to the same fetch, up to the @@ -6317,7 +5901,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; max-clients-per-query is not effective as a limit.

-

+

Optionally, this value may be followed by the keyword drop or fail, indicating whether queries which exceed the fetch @@ -6325,12 +5909,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; or answered with SERVFAIL. The default is drop.

-

+

If fetches-per-zone is set to zero, then there is no limit on the number of fetches per query and no queries will be dropped. The default is zero.

-

+

The current list of active fetches can be dumped by running rndc recursing. The list includes the number of active fetches for each @@ -6343,12 +5927,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; next time a fetch is sent to that domain, it is recreated with the counters set to zero.)

-
+
fetches-per-server
-

+

The maximum number of simultaneous iterative queries that the server will allow to be sent to a single upstream name server before blocking @@ -6358,7 +5942,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; would take to resolve them. It should be smaller than recursive-clients.

-

+

Optionally, this value may be followed by the keyword drop or fail, indicating whether queries will be dropped with no @@ -6367,12 +5951,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; exceeded the per-server quota. The default is fail.

-

+

If fetches-per-server is set to zero, then there is no limit on the number of fetches per query and no queries will be dropped. The default is zero.

-

+

The fetches-per-server quota is dynamically adjusted in response to detected congestion. As queries are sent to a server @@ -6388,15 +5972,15 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; can be used to adjust the parameters for this calculation.

-
+
fetch-quota-params
-

+

Sets the parameters to use for dynamic resizing of the fetches-per-server quota in response to detected congestion.

-

+

The first argument is an integer value indicating how frequently to recalculate the moving average of the ratio of timeouts to responses for each @@ -6404,7 +5988,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; the average ratio after every 100 queries have either been answered or timed out.

-

+

The remaining three arguments represent the "low" threshold (defaulting to a timeout ratio of 0.1), the "high" threshold (defaulting to a timeout @@ -6419,10 +6003,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; precision of 1/100: at most two places after the decimal point are significant.

-
+
reserved-sockets
-

+

The number of file descriptors reserved for TCP, stdio, etc. This needs to be big enough to cover the number of interfaces named listens on, tcp-clients as well as @@ -6432,13 +6016,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; maximum value is 128 less than maxsockets (-S). This option may be removed in the future.

-

+

This option has little effect on Windows.

-
+
max-cache-size
-
-

+

The maximum amount of memory to use for the server's cache, in bytes or % of total physical memory. When the amount of data in the cache @@ -6461,11 +6044,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; once at startup, so named will not adjust the cache size if the amount of physical memory is changed during runtime. -

-
+

tcp-listen-queue
-
-

+

The listen queue depth. The default and minimum is 10. If the kernel supports the accept filter "dataready" this also controls how @@ -6475,11 +6056,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; less than 10 will be silently raised. A value of 0 may also be used; on most platforms this sets the listen queue length to a system-defined default value. -

-
+

tcp-initial-timeout
-
-

+

The amount of time (in units of 100 milliseconds) the server waits on a new TCP connection for the first message from the client. The default is 300 (30 seconds), @@ -6491,11 +6070,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; have enough time to submit a message.) This value can be updated at runtime by using rndc tcp-timeouts. -

-
+

tcp-idle-timeout
-
-

+

The amount of time (in units of 100 milliseconds) the server waits on an idle TCP connection before closing it when the client is not using the EDNS TCP keepalive @@ -6507,11 +6084,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; for clients using the EDNS TCP keepalive option. This value can be updated at runtime by using rndc tcp-timeouts. -

-
+

tcp-keepalive-timeout
-
-

+

The amount of time (in units of 100 milliseconds) the server waits on an idle TCP connection before closing it when the client is using the EDNS TCP keepalive @@ -6525,11 +6100,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; to use TCP connections for more than one message. This value can be updated at runtime by using rndc tcp-timeouts. -

-
+

tcp-advertised-timeout
-
-

+

The timeout value (in units of 100 milliseconds) the server will send in respones containing the EDNS TCP keepalive option. This informs a client of the @@ -6541,20 +6114,15 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; same value as tcp-keepalive-timeout. This value can be updated at runtime by using rndc tcp-timeouts. -

-
+

- -
- -
+
+

Periodic Task Intervals

- -
+
cleaning-interval
-
-

+

This interval is effectively obsolete. Previously, the server would remove expired resource records from the cache every cleaning-interval minutes. @@ -6563,11 +6131,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; rely on the periodic cleaning any more. Specifying this option therefore has no effect on the server's behavior. -

-
+

heartbeat-interval
-
-

+

The server will perform zone maintenance tasks for all zones marked as dialup whenever this interval expires. The default is 60 minutes. Reasonable @@ -6575,11 +6141,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; to 1 day (1440 minutes). The maximum value is 28 days (40320 minutes). If set to 0, no zone maintenance for these zones will occur. -

-
+

interface-interval
-
-

+

The server will scan the network interface list every interface-interval minutes. The default @@ -6593,11 +6157,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; will stop listening on interfaces that have gone away. For convenience, TTL-style time unit suffixes may be used to specify the value. -

-
+

statistics-interval
-

+

Name server statistics will be logged every statistics-interval minutes. The default is @@ -6606,30 +6169,25 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };

Note

-

+

Not yet implemented in BIND 9.

-
-
+
+
topology
-
-

+

In BIND 8, this option indicated network topology so that preferential treatment could be given to the topologicaly closest name servers when sending queries. It is not implemented in BIND 9. -

-
+

- -
- -
+
+

The sortlist Statement

- -

+

The response to a DNS query may consist of multiple resource records (RRs) forming a resource record set (RRset). The name server will normally return the RRs within the RRset in an @@ -6643,8 +6201,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; client's address. This only requires configuring the name servers, not all the clients.

- -

+

The sortlist statement (see below) takes an address_match_list and interprets it in a special way. Each top level statement in the @@ -6655,7 +6212,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; each top level list is checked against the source address of the query until a match is found.

-

+

Once the source address of the query has been matched, if the top level statement contains only one element, the actual primitive element that matched the source address is used to @@ -6666,7 +6223,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; address in the response with the minimum distance is moved to the beginning of the response.

-

+

In the following example, any queries received from any of the addresses of the host itself will get responses preferring addresses on any of the locally connected networks. Next most @@ -6679,7 +6236,6 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; the 192.168.5/24 network will only prefer other addresses on their directly connected networks.

- 
sortlist {
     // IF the local host
     // THEN first fit on the following nets
@@ -6703,8 +6259,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
     { { 192.168.4/24; 192.168.5/24; };
     };
 };
- -

+

The following example will give reasonable behavior for the local host and hosts on directly connected networks. It is similar to the behavior of the address sort in @@ -6714,19 +6269,16 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; directly connected network will prefer addresses on that same network. Responses to other queries will not be sorted.

- 
sortlist {
            { localhost; localnets; };
            { localnets; };
 };
- -
-
+
+

RRset Ordering

- -

+

When multiple records are returned in an answer it may be useful to configure the order of the records placed into the response. The rrset-order statement permits @@ -6735,25 +6287,24 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; See also the sortlist statement, the section called “The sortlist Statement”.

-

+

An order_spec is defined as follows:

-

+

[class class_name] [type type_name] [name "domain_name"] order ordering

-

+

If no class is specified, the default is ANY. If no type is specified, the default is ANY. If no name is specified, the default is "*" (asterisk).

-

+

The legal values for ordering are:

-
- +
@@ -6779,8 +6330,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; @@ -6811,16 +6361,16 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; Records are returned in whatever order they were retrieved from the database. This order is indeterminate, but will be consistent as long as the - database is not modified. + database is not modified. When no ordering is + specified, this is the default.

-

- Records are returned in some random order. When no - ordering is specified, this is the default. + Records are returned in some random order.

-
-

+

+

-

+

For example: 

rrset-order {
@@ -6828,53 +6378,47 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };
    order cyclic;
 };
-

+

will cause any responses for type A records in class IN that have "host.example.com" as a suffix, to always be returned in random order. All other records are returned in cyclic order.

-

+

If multiple rrset-order statements appear, they are not combined — the last one applies.

-

+

By default, records are returned in indeterminate but consistent order (see none above).

- -
+

Note

-

+

In this release of BIND 9, the rrset-order statement does not support "fixed" ordering by default. Fixed ordering can be enabled at compile time by specifying "--enable-fixed-rrset" on the "configure" command line.

-
-
- -
+
+
+

Tuning

- -
+
lame-ttl
-
-

+

Sets the number of seconds to cache a lame server indication. 0 disables caching. (This is NOT recommended.) The default is 600 (10 minutes) and the maximum value is 1800 (30 minutes). -

- -
+

servfail-ttl
-

+

Sets the number of seconds to cache a SERVFAIL response due to DNSSEC validation failure or other general server failure. If set to @@ -6884,16 +6428,15 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; query that failed due to DNSSEC validation to be retried without waiting for the SERVFAIL TTL to expire.

-

+

The maximum value is 30 seconds; any higher value will be silently reduced. The default is 1 second.

-
+
max-ncache-ttl
-
-

+

To reduce network traffic and increase performance, the server stores negative answers. max-ncache-ttl is used to set a maximum retention time for these answers in @@ -6904,11 +6447,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; max-ncache-ttl cannot exceed 7 days and will be silently truncated to 7 days if set to a greater value. -

-
+

max-cache-ttl
-
-

+

Sets the maximum time for which the server will cache ordinary (positive) answers in seconds. For convenience, TTL-style time unit suffixes may be @@ -6918,11 +6459,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; SERVFAIL, because of lost caches of intermediate RRsets (such as NS and glue AAAA/A records) in the resolution process. -

-
+

max-stale-ttl
-

+

If stale answers are enabled, max-stale-ttl sets the maximum time for which the server will @@ -6933,31 +6473,31 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; 1 second; a value of 0 will be updated silently to 1 second.

-

+

For stale answers to be returned, they must be enabled, either in the configuration file using stale-answer-enable or via rndc serve-stale on.

-
+
min-roots
-

+

The minimum number of root servers that is required for a request for the root servers to be accepted. The default is 2.

-
+

Note

-

+

Not implemented in BIND 9.

-
-
+
+
sig-validity-interval
-

+

Specifies the number of days into the future when DNSSEC signatures automatically generated as a result of dynamic updates (the section called “Dynamic Update”) will expire. There @@ -6971,26 +6511,25 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; giving a re-signing interval of 7 1/2 days. The maximum values are 10 years (3660 days).

-

+

The signature inception time is unconditionally set to one hour before the current time to allow for a limited amount of clock skew.

-

+

The sig-validity-interval can be overridden for DNSKEY records by setting dnskey-sig-validity.

-

+

The sig-validity-interval should be, at least, several multiples of the SOA expire interval to allow for reasonable interaction between the various timer and expiry dates.

-
+
dnskey-sig-validity
-
-

+

Specifies the number of days into the future when DNSSEC signatures that are automatically generated for DNSKEY RRsets as a result of dynamic updates @@ -7001,38 +6540,33 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; sig-validity-interval is used. The maximum value is 3660 days (10 years), and higher values will be rejected. -

-
+

sig-signing-nodes
-
-

+

Specify the maximum number of nodes to be examined in each quantum when signing a zone with a new DNSKEY. The default is 100. -

-
+

sig-signing-signatures
-
-

+

Specify a threshold number of signatures that will terminate processing a quantum when signing a zone with a new DNSKEY. The default is 10. -

-
+

sig-signing-type
-

+

Specify a private RDATA type to be used when generating signing state records. The default is 65534.

-

+

It is expected that this parameter may be removed in a future version once there is a standard type.

-

+

Signing state records are used to internally by named to track the current state of a zone-signing process, i.e., whether it is still active @@ -7048,12 +6582,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; records for a zone, use rndc signing -clear all zone.

-
+
min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
-

+

These options control the server's behavior on refreshing a zone (querying for SOA changes) or retrying failed transfers. Usually the SOA values for the zone are used, @@ -7061,14 +6595,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; these values are set by the master, giving slave server administrators little control over their contents.

-

+

These options allow the administrator to set a minimum and maximum refresh and retry time in seconds per-zone, per-view, or globally. These options are valid for slave and stub zones, and clamp the SOA refresh and retry times to the specified values.

-

+

The following defaults apply. min-refresh-time 300 seconds, max-refresh-time 2419200 seconds @@ -7076,10 +6610,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; and max-retry-time 1209600 seconds (2 weeks).

-
+
edns-udp-size
-

+

Sets the maximum advertised EDNS UDP buffer size in bytes, to control the size of packets received from authoritative servers in response to recursive queries. @@ -7087,19 +6621,19 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; will be silently adjusted to the nearest value within it). The default value is 4096.

-

+

The usual reason for setting edns-udp-size to a non-default value is to get UDP answers to pass through broken firewalls that block fragmented packets and/or block UDP DNS packets that are greater than 512 bytes.

-

+

When named first queries a remote server, it will advertise a UDP buffer size of 512, as this has the greatest chance of success on the first try.

-

+

If the initial response times out, named will try again with plain DNS, and if that is successful, it will be taken as evidence that the server does not @@ -7110,7 +6644,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; will send an EDNS query to see if the situation has improved.)

-

+

However, if the initial query is successful with EDNS advertising a buffer size of 512, then named will advertise progressively @@ -7118,7 +6652,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; responses begin timing out or edns-udp-size is reached.

-

+

The default buffer sizes used by named are 512, 1232, 1432, and 4096, but never exceeding edns-udp-size. (The values 1232 and @@ -7126,22 +6660,22 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; UDP message to be sent without fragmentation at the minimum MTU sizes for Ethernet and IPv6 networks.)

-
+
max-udp-size
-

+

Sets the maximum EDNS UDP message size named will send in bytes. Valid values are 512 to 4096 (values outside this range will be silently adjusted to the nearest value within it). The default value is 4096.

-

+

This value applies to responses sent by a server; to set the advertised buffer size in queries, see edns-udp-size.

-

+

The usual reason for setting max-udp-size to a non-default value is to get UDP answers to pass through broken @@ -7150,14 +6684,14 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; This is independent of the advertised receive buffer (edns-udp-size).

-

+

Setting this to a low value will encourage additional TCP traffic to the nameserver.

-
+
masterfile-format
-

Specifies +

Specifies the file format of zone files (see the section called “Additional File Formats”). The default value is text, which is the @@ -7168,7 +6702,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; named-compilezone tool, or dumped by named.

-

+

Note that when a zone file in a different format than text is loaded, named may omit some of the checks which would be performed for a @@ -7182,7 +6716,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; loaded directly into memory via memory mapping, with only minimal checking.

-

+

This statement sets the masterfile-format for all zones, but can be overridden on a per-zone or per-view basis @@ -7191,16 +6725,16 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; view block in the configuration file.

-
+
masterfile-style
-

+

Specifies the formatting of zone files during dump when the masterfile-format is text. (This option is ignored with any other masterfile-format.)

-

+

When set to relative, records are printed in a multi-line format with owner names expressed relative to a shared origin. When set @@ -7213,12 +6747,11 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; zone is to be edited by hand. The default is relative.

-
+
max-recursion-depth
-
-

+

Sets the maximum number of levels of recursion that are permitted at any one time while servicing a recursive query. Resolving a name may require @@ -7227,13 +6760,11 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; of indirections exceeds this value, the recursive query is terminated and returns SERVFAIL. The default is 7. -

-
+

max-recursion-queries
-
-

+

Sets the maximum number of iterative queries that may be sent while servicing a recursive query. If more queries are sent, the recursive query @@ -7241,38 +6772,35 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; look up top level domains such as "com" and "net" and the DNS root zone are exempt from this limitation. The default is 75. -

-
+

notify-delay
-

+

The delay, in seconds, between sending sets of notify messages for a zone. The default is five (5) seconds.

-

+

The overall rate that NOTIFY messages are sent for all zones is controlled by serial-query-rate.

-
+
max-rsa-exponent-size
-
-

+

The maximum RSA exponent size, in bits, that will be accepted when validating. Valid values are 35 to 4096 bits. The default zero (0) is also accepted and is equivalent to 4096. -

-
+

prefetch
-

+

When a query is received for cached data which is to expire shortly, named can refresh the data from the authoritative server immediately, ensuring that the cache always has an answer available.

-

+

The prefetch specifies the "trigger" TTL value at which prefetch of the current query will take place: when a cache record with a @@ -7284,7 +6812,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; prefetch to be disabled. The default trigger TTL is 2.

-

+

An optional second argument specifies the "eligibility" TTL: the smallest original TTL value that will be accepted for a record to be @@ -7294,24 +6822,19 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; adjust it upward. The default eligibility TTL is 9.

-
+
v6-bias
-
-

+

When determining the next nameserver to try preference IPv6 nameservers by this many milliseconds. The default is 50 milliseconds. -

-
+

- -
- -
+
+

Built-in server information zones

- -

+

The server provides some helpful diagnostic information through a number of built-in zones under the pseudo-top-level-domain bind in the @@ -7330,29 +6853,25 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; rate-limit is set to allow three responses per second.

-

+

If you need to disable these zones, use the options below, or hide the built-in CHAOS view by defining an explicit view of class CHAOS that matches all clients.

- -
+
version
-
-

+

The version the server should report via a query of the name version.bind with type TXT, class CHAOS. The default is the real version number of this server. Specifying version none disables processing of the queries. -

-
+

hostname
-
-

+

The hostname the server should report via a query of the name hostname.bind with type TXT, class CHAOS. @@ -7363,11 +6882,9 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; identify which of a group of anycast servers is actually answering your queries. Specifying hostname none; disables processing of the queries. -

-
+

server-id
-
-

+

The ID the server should report when receiving a Name Server Identifier (NSID) query, or a query of the name ID.SERVER with type @@ -7379,17 +6896,13 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; Specifying server-id hostname; will cause named to use the hostname as found by the gethostname() function. The default server-id is none. -

-
+

- -
- -
+
+

Built-in Empty Zones

- -

+

The named server has some built-in empty zones (SOA and NS records only). These are for zones that should normally be answered locally @@ -7402,13 +6915,13 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; IPv6 link local addresses, the IPv6 loopback address and the IPv6 unknown address.

-

+

The server will attempt to determine if a built-in zone already exists or is active (covered by a forward-only forwarding declaration) and will not create an empty zone in that case.

-

+

The current list of empty zones is:

    @@ -7514,7 +7027,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };

-

+

Empty zones are settable at the view level and only apply to views of class IN. Disabled empty zones are only inherited from options if there are no disabled empty zones specified @@ -7526,7 +7039,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; };

-

+

If you are using the address ranges covered here, you should already have reverse zones covering the addresses you use. In practice this appears to not be the case with many queries @@ -7535,7 +7048,7 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; to be deployed to channel the query load away from the infrastructure servers.

-
+

Note

The real parent servers for these zones should disable all @@ -7544,45 +7057,35 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; enable them to return referrals to deeper in the tree.

-
+
empty-server
-
-

+

Specify what server name will appear in the returned SOA record for empty zones. If none is specified, then the zone's name will be used. -

-
+

empty-contact
-
-

+

Specify what contact name will appear in the returned SOA record for empty zones. If none is specified, then "." will be used. -

-
+

empty-zones-enable
-
-

+

Enable or disable all empty zones. By default, they are enabled. -

-
+

disable-empty-zone
-
-

+

Disable individual empty zones. By default, none are disabled. This option can be specified multiple times. -

-
+

-
- -
+
+

Content Filtering

- -

+

BIND 9 provides the ability to filter out DNS responses from external DNS servers containing certain types of data in the answer section. @@ -7608,12 +7111,10 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; deny-answer-aliases, 

www.example.com. CNAME xxx.example.com.
- -

+

returned by an "example.com" server will be accepted.

- -

+

In the address_match_list of the deny-answer-addresses option, only ip_addr @@ -7621,14 +7122,12 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; are meaningful; any key_id will be silently ignored.

- -

+

If a response message is rejected due to the filtering, the entire message is discarded without being cached, and a SERVFAIL error will be returned to the client.

- -

+

This filtering is intended to prevent "DNS rebinding attacks," in which an attacker, in response to a query for a domain name the attacker controls, returns an IP address within your own network or @@ -7643,48 +7142,39 @@ avoid-v6-udp-ports { 40000; range 50000 60000; }; for more details about the attacks.

- -

+

For example, if you own a domain named "example.net" and your internal network uses an IPv4 prefix 192.0.2.0/24, you might specify the following rules:

- 
deny-answer-addresses { 192.0.2.0/24; } except-from { "example.net"; };
 deny-answer-aliases { "example.net"; };
- -

+

If an external attacker lets a web browser in your local network look up an IPv4 address of "attacker.example.com", the attacker's DNS server would return a response like this:

- 
attacker.example.com. A 192.0.2.1
- -

+

in the answer section. Since the rdata of this record (the IPv4 address) matches the specified prefix 192.0.2.0/24, this response will be ignored.

- -

+

On the other hand, if the browser looks up a legitimate internal web server "www.example.net" and the following response is returned to the BIND 9 server

- 
www.example.net. A 192.0.2.2
- -

+

it will be accepted since the owner name "www.example.net" matches the except-from element, "example.net".

- -

+

Note that this is not really an attack on the DNS per se. In fact, there is nothing wrong for an "external" name to be mapped to your "internal" IP address or domain name @@ -7705,8 +7195,7 @@ deny-answer-aliases { "example.net"; }; very sure you have no other choice and the attack is a real threat for your applications.

- -

+

Care should be particularly taken if you want to use this option for addresses within 127.0.0.0/8. These addresses are obviously "internal", but many @@ -7715,13 +7204,11 @@ deny-answer-aliases { "example.net"; }; Filtering out DNS records containing this address spuriously can break such applications.

-
- -
+
+

Response Policy Zone (RPZ) Rewriting

- -

+

BIND 9 includes a limited mechanism to modify DNS responses for requests analogous to email anti-spam DNS blacklists. @@ -7729,8 +7216,7 @@ deny-answer-aliases { "example.net"; }; deny the existence of IP addresses for domains (NODATA), or contain other IP addresses or data.

- -

+

Response policy zones are named in the response-policy option for the view or among the global options if there is no response-policy option for the view. @@ -7741,8 +7227,7 @@ deny-answer-aliases { "example.net"; }; Note that zones using masterfile-format map cannot be used as policy zones.

- -

+

A response-policy option can support multiple policy zones. To maximize performance, a radix tree is used to quickly identify response policy zones @@ -7751,14 +7236,13 @@ deny-answer-aliases { "example.net"; }; in a single response-policy option; more than that is a configuration error.

- -

+

Five policy triggers can be encoded in RPZ records.

RPZ-CLIENT-IP
-

+

IP records are triggered by the IP address of the DNS client. Client IP address triggers are encoded in records that have @@ -7773,8 +7257,7 @@ deny-answer-aliases { "example.net"; }; B4 is the decimal value of the least significant byte of the IPv4 address as in IN-ADDR.ARPA.

- -

+

IPv6 addresses are encoded in a format similar to the standard IPv6 text representation, prefixlength.W8.W7.W6.W5.W4.W3.W2.W1.rpz-client-ip. @@ -7790,29 +7273,24 @@ deny-answer-aliases { "example.net"; }; encodings. The IPv6 prefix length must be between 1 and 128.

-
+
QNAME
-
-

+

QNAME policy records are triggered by query names of requests and targets of CNAME records resolved to generate the response. The owner name of a QNAME policy record is the query name relativized to the policy zone. -

-
+

RPZ-IP
-
-

+

IP triggers are IP addresses in an A or AAAA record in the ANSWER section of a response. They are encoded like client-IP triggers except as subdomains of rpz-ip. -

-
+

RPZ-NSDNAME
-
-

+

NSDNAME triggers match names of authoritative servers for the query name, a parent of the query name, a CNAME for query name, or a parent of a CNAME. @@ -7825,11 +7303,10 @@ deny-answer-aliases { "example.net"; }; The nsdname-enable phrase turns NSDNAME triggers off or on for a single policy zone or all zones. -

-
+

RPZ-NSIP
-

+

NSIP triggers match the IP addresses of authoritative servers. They are enncoded like IP triggers, except as subdomains of rpz-nsip. @@ -7841,7 +7318,7 @@ deny-answer-aliases { "example.net"; }; triggers off or on for a single policy zone or all zones.

-

+

If a name server's IP address is not yet known, named will recursively look up the IP address before applying an RPZ-NSIP rule. @@ -7860,12 +7337,11 @@ deny-answer-aliases { "example.net"; }; rules should always be applied even if an address needs to be looked up first.

-
+

- -

+

The query response is checked against all response policy zones, so two or more policy records can be triggered by a response. Because DNS responses are rewritten according to at most one @@ -7894,16 +7370,14 @@ deny-answer-aliases { "example.net"; };

- -

+

When the processing of a response is restarted to resolve DNAME or CNAME records and a policy record set has not been triggered, all response policy zones are again consulted for the DNAME or CNAME names and addresses.

- -

+

RPZ record sets are any types of DNS record except DNAME or DNSSEC that encode actions or responses to individual queries. @@ -7915,59 +7389,48 @@ deny-answer-aliases { "example.net"; };

PASSTHRU
-
-

+

The whitelist policy is specified by a CNAME whose target is rpz-passthru. It causes the response to not be rewritten and is most often used to "poke holes" in policies for CIDR blocks. -

-
+

DROP
-
-

+

The blacklist policy is specified by a CNAME whose target is rpz-drop. It causes the response to be discarded. Nothing is sent to the DNS client. -

-
+

TCP-Only
-
-

+

The "slip" policy is specified by a CNAME whose target is rpz-tcp-only. It changes UDP responses to short, truncated DNS responses that require the DNS client to try again with TCP. It is used to mitigate distributed DNS reflection attacks. -

-
+

NXDOMAIN
-
-

+

The domain undefined response is encoded by a CNAME whose target is the root domain (.) -

-
+

NODATA
-
-

+

The empty set of resource records is specified by CNAME whose target is the wildcard top-level domain (*.). It rewrites the response to NODATA or ANCOUNT=1. -

-
+

Local Data
-

+

A set of ordinary DNS records can be used to answer queries. Queries for record types not the set are answered with NODATA.

- -

+

A special form of local data is a CNAME whose target is a wildcard such as *.example.com. It is used as if were an ordinary CNAME after the asterisk (*) @@ -7975,12 +7438,11 @@ deny-answer-aliases { "example.net"; }; The purpose for this special form is query logging in the walled garden's authority DNS server.

-
+

- -

+

All of the actions specified in all of the individual records in a policy zone can be overridden with a policy clause in the @@ -7991,14 +7453,11 @@ deny-answer-aliases { "example.net"; };

GIVEN
-
-

The placeholder policy says "do not override but +

The placeholder policy says "do not override but perform the action specified in the zone." -

-
+

DISABLED
-
-

+

The testing override policy causes policy zone records to do nothing but log what they would have done if the policy zone were not disabled. @@ -8008,28 +7467,22 @@ deny-answer-aliases { "example.net"; }; Disabled policy zones should appear first, because they will often not be logged if a higher precedence trigger is found first. -

-
+

PASSTHRU, DROP, TCP-Only, NXDOMAIN, NODATA
-
-

+

override with the corresponding per-record policy. -

-
+

CNAME domain
-
-

+

causes all RPZ policy records to act as if they were "cname domain" records. -

-
+

- -

+

By default, the actions encoded in a response policy zone are applied only to queries that ask for recursion (RD=1). That default can be changed for a single policy zone or @@ -8040,8 +7493,7 @@ deny-answer-aliases { "example.net"; }; delete answers that would otherwise contain RFC 1918 values on the externally visible name server or view.

- -

+

Also by default, RPZ actions are applied only to DNS requests that either do not request DNSSEC metadata (DO=0) or when no DNSSEC records are available for request name in the original @@ -8052,8 +7504,7 @@ deny-answer-aliases { "example.net"; }; clause option reflects the fact that results rewritten by RPZ actions cannot verify.

- -

+

No DNS records are needed for a QNAME or Client-IP trigger. The name or IP address itself is sufficient, so in principle the query name need not be recursively resolved. @@ -8080,15 +7531,13 @@ deny-answer-aliases { "example.net"; }; appear to be rewritten, since no recursion is being done to discover problems at the authoritative server.

- -

+

The dnsrps-enable yes option turns on the DNS Rsponse Policy Service (DNSRPS) interface, if it has been compiled in to named using configure --enable-dnsrps.

- -

+

The dnsrps-options block provides additional RPZ configuration settings, which are passed through to the DNSRPS provider library. @@ -8099,8 +7548,7 @@ deny-answer-aliases { "example.net"; }; concatenated with settings derived from the response-policy statement.

- -

+

Note: The dnsrps-options text should only include configuration settings that are specific to the DNSRPS provider. For example, the DNSRPS provider from @@ -8116,8 +7564,7 @@ deny-answer-aliases { "example.net"; }; dnsrps-enable to "no", those options would be ignored.

- -

+

The TTL of a record modified by RPZ policies is set from the TTL of the relevant record in policy zone. It is then limited to a maximum value. @@ -8126,16 +7573,15 @@ deny-answer-aliases { "example.net"; }; For convenience, TTL-style time unit suffixes may be used to specify the value.

- -

+

For example, you might use this option statement 

    response-policy { zone "badlist"; };
-

+

and this zone statement 

    zone "badlist" {type master; file "master/badlist"; allow-query {none;}; };
-

+

with this zone file 

$TTL 1H
@@ -8177,7 +7623,7 @@ example.com                 CNAME   rpz-tcp-only.
 *.example.com               CNAME   rpz-tcp-only.
-

+

RPZ can affect server performance. Each configured response policy zone requires the server to perform one to four additional database lookups before a @@ -8192,19 +7638,16 @@ example.com CNAME rpz-tcp-only. A server with four response policy zones with QNAME and IP triggers might have a maximum QPS rate about 50% lower.

- -

+

Responses rewritten by RPZ are counted in the RPZRewrites statistics.

- -

+

The log clause can be used to optionally turn off rewrite logging for a particular response policy zone. By default, all rewrites are logged.

- -

+

Updates to RPZ zones are processed asynchronously; if there is more than one update pending they are bundled together. If an update to a RPZ zone (for example, via IXFR) happens less @@ -8214,13 +7657,11 @@ example.com CNAME rpz-tcp-only. For convenience, TTL-style time unit suffixes may be used to specify the value.

-
- -
+
+

Response Rate Limiting

- -

+

Excessive almost identical UDP responses can be controlled by configuring a rate-limit clause in an @@ -8233,8 +7674,7 @@ example.com CNAME rpz-tcp-only. Legitimate clients react to dropped or truncated response by retrying with UDP or with TCP respectively.

- -

+

This mechanism is intended for authoritative DNS servers. It can be used on recursive servers but can slow applications such as SMTP servers (mail receivers) and @@ -8242,8 +7682,7 @@ example.com CNAME rpz-tcp-only. same domains. When possible, closing "open" recursive servers is better.

- -

+

Response rate limiting uses a "credit" or "token bucket" scheme. Each combination of identical response and client has a conceptual account that earns a specified number @@ -8262,8 +7701,7 @@ example.com CNAME rpz-tcp-only. When the specified number of credits for a class of responses is set to 0, those responses are not rate limited.

- -

+

The notions of "identical response" and "DNS client" for rate limiting are not simplistic. All responses to an address block are counted as if to a @@ -8272,8 +7710,7 @@ example.com CNAME rpz-tcp-only. specified with ipv4-prefix-length (default 24) and ipv6-prefix-length (default 56).

- -

+

All non-empty responses for a valid domain name (qname) and record type (qtype) are identical and have a limit specified with responses-per-second @@ -8297,14 +7734,12 @@ example.com CNAME rpz-tcp-only. referrals-per-second (default responses-per-second).

- -

+

Responses generated from local wildcards are counted and limited as if they were for the parent domain name. This controls flooding using random.wild.example.com.

- -

+

All requests that result in DNS errors other than NXDOMAIN, such as SERVFAIL and FORMERR, are identical regardless of requested name (qname) or record type (qtype). @@ -8315,8 +7750,7 @@ example.com CNAME rpz-tcp-only. but it can be set separately with errors-per-second.

- -

+

Many attacks using DNS involve UDP requests with forged source addresses. Rate limiting prevents the use of BIND 9 to flood a network @@ -8340,8 +7774,7 @@ example.com CNAME rpz-tcp-only. cannot be replaced with truncated responses and are instead leaked at the slip rate.

- -

+

(NOTE: Dropped responses from an authoritative server may reduce the difficulty of a third party successfully forging a response to a recursive resolver. The best security @@ -8354,8 +7787,7 @@ example.com CNAME rpz-tcp-only. responses to be truncated rather than dropped. This reduces the effectiveness of rate-limiting against reflection attacks.)

- -

+

When the approximate query per second rate exceeds the qps-scale value, then the responses-per-second, @@ -8373,24 +7805,21 @@ example.com CNAME rpz-tcp-only. Responses sent via TCP are not limited but are counted to compute the query per second rate.

- -

+

Rate limiters for different name spaces maintain separate counters: If, for example, there is a rate-limit statement for "com" and another for "example.com", queries matching "example.com" will not be debited against the rate limiter for "com".

- -

+

If a rate-limit statement does not specify a domain, then it applies to the root domain (".") and thus affects the entire DNS namespace, except those portions covered by other rate-limit statements.

- -

+

Communities of DNS clients can be given their own parameters or no rate limiting by putting rate-limit statements in view @@ -8402,8 +7831,7 @@ example.com CNAME rpz-tcp-only. DNS clients within a view can be exempted from rate limits with the exempt-clients clause.

- -

+

UDP responses of all kinds can be limited with the all-per-second phrase. This rate limiting is unlike the rate limiting provided by @@ -8436,8 +7864,7 @@ example.com CNAME rpz-tcp-only. or parsing DNS requests, but that rate limiting must be done before the DNS server sees the requests.

- -

+

The maximum size of the table used to track requests and rate limit responses is set with max-table-size. Each entry in the table is between 40 and 80 bytes. @@ -8451,24 +7878,21 @@ example.com CNAME rpz-tcp-only. expansions of the table and inform choices for the initial and maximum table size.

- -

+

Use log-only yes to test rate limiting parameters without actually dropping any requests.

- -

+

Responses dropped by rate limits are included in the RateDropped and QryDropped statistics. Responses that truncated by rate limits are included in RateSlipped and RespTruncated.

-
- -
+
+
-

+

Named supports NXDOMAIN redirection via two methods:

    @@ -8479,19 +7903,19 @@ example.com CNAME rpz-tcp-only.

-

+

With both methods when named gets a NXDOMAIN response it examines a separate namespace to see if the NXDOMAIN response should be replaced with an alternative response.

-

+

With a redirect zone (zone "." { type redirect; };), the data used to replace the NXDOMAIN is held in a single zone which is not part of the normal namespace. All the redirect information is contained in the zone; there are no delegations.

-

+

With a redirect namespace (option { nxdomain-redirect <suffix> };) the data used to replace the NXDOMAIN is part of the normal namespace and is looked up by @@ -8501,17 +7925,16 @@ example.com CNAME rpz-tcp-only. the replacement data or a NXDOMAIN indicating that there is no replacement.

-

+

If both a redirect zone and a redirect namespace are configured, the redirect zone is tried first.

-
-
- -
+
+
+

server Statement Grammar

- 
+
 server netprefix {
 	bogus boolean;
 	edns boolean;
@@ -8545,14 +7968,12 @@ example.com                 CNAME   rpz-tcp-only.
 	transfers integer;
 };
 

-
- -
+
+

server Statement Definition and Usage

- -

+

The server statement defines characteristics to be associated with a remote name server. If a prefix length is @@ -8561,8 +7982,7 @@ example.com CNAME rpz-tcp-only. server clause applies regardless of the order in named.conf.

- -

+

The server statement can occur at the top level of the configuration file or inside a view @@ -8577,14 +7997,13 @@ example.com CNAME rpz-tcp-only. used as defaults.

- -

+

If you discover that a remote server is giving out bad data, marking it as bogus will prevent further queries to it. The default value of bogus is no.

-

+

The provide-ixfr clause determines whether the local server, acting as master, will respond with an @@ -8600,8 +8019,7 @@ example.com CNAME rpz-tcp-only. view or global options block is used as a default.

- -

+

The request-ixfr clause determines whether the local server, acting as a slave, will request incremental zone @@ -8611,8 +8029,7 @@ example.com CNAME rpz-tcp-only. also be set in the zone block and, if set there, it will override the global or view setting for that zone.

- -

+

IXFR requests to servers that do not support IXFR will automatically fall back to AXFR. Therefore, there is no need to manually list @@ -8626,8 +8043,7 @@ example.com CNAME rpz-tcp-only. and slave claim to support it, for example if one of the servers is buggy and crashes or corrupts data when IXFR is used.

- -

+

The request-expire clause determines whether the local server, when acting as a slave, will request the EDNS EXPIRE value. The EDNS EXPIRE value @@ -8639,14 +8055,12 @@ example.com CNAME rpz-tcp-only. record instead. The default is yes.

- -

+

The edns clause determines whether the local server will attempt to use EDNS when communicating with the remote server. The default is yes.

- -

+

The edns-udp-size option sets the EDNS UDP size that is advertised by named when querying the remote server. Valid values are 512 @@ -8665,8 +8079,7 @@ example.com CNAME rpz-tcp-only. behavior may be brought into conformance with the options/view behavior in future releases.)

- -

+

The edns-version option sets the maximum EDNS VERSION that will be sent to the server(s) by the resolver. The actual EDNS version sent is still @@ -8681,8 +8094,7 @@ example.com CNAME rpz-tcp-only. adjusted. This option will not be needed until higher EDNS versions than 0 are in use.

- -

+

The max-udp-size option sets the maximum EDNS UDP message size named will send. Valid values are 512 to 4096 bytes (values @@ -8690,8 +8102,7 @@ example.com CNAME rpz-tcp-only. option is useful when you know that there is a firewall that is blocking large replies from named.

- -

+

The padding option adds EDNS Padding options to outgoing messages, increasing the packet size to a multiple of the specified block size. Valid block sizes @@ -8703,21 +8114,18 @@ example.com CNAME rpz-tcp-only. would have to be added to the packet after it had already been signed.

- -

+

The tcp-only option sets the transport protocol to TCP. The default is to use the UDP transport and to fallback on TCP only when a truncated response is received.

- -

+

The tcp-keepalive option adds EDNS TCP keepalive to messages sent over TCP. Note currently idle timeouts in responses are ignored.

- -

+

The server supports two zone transfer methods. The first, one-answer, uses one DNS message per resource record transferred. many-answers packs as many resource records as possible into a message. many-answers is @@ -8731,16 +8139,14 @@ example.com CNAME rpz-tcp-only. by the options statement will be used.

- -

transfers +

transfers is used to limit the number of concurrent inbound zone transfers from the specified server. If no transfers clause is specified, the limit is set according to the transfers-per-ns option.

- -

+

The keys clause identifies a key_id defined by the key statement, to be used for transaction security (TSIG, the section called “TSIG”) @@ -8751,12 +8157,10 @@ example.com CNAME rpz-tcp-only. required to be signed by this key.

- -

+

Only a single key per server is currently supported.

- -

+

The transfer-source and transfer-source-v6 clauses specify the IPv4 and IPv6 source @@ -8772,8 +8176,7 @@ example.com CNAME rpz-tcp-only. transfer-source-v6 in the section called “Zone Transfers”.

- -

+

The notify-source and notify-source-v6 clauses specify the IPv4 and IPv6 source address to be used for notify @@ -8782,8 +8185,7 @@ example.com CNAME rpz-tcp-only. can be specified. Similarly, for an IPv6 remote server, only notify-source-v6 can be specified.

- -

+

The query-source and query-source-v6 clauses specify the IPv4 and IPv6 source address to be used for queries @@ -8792,16 +8194,14 @@ example.com CNAME rpz-tcp-only. be specified. Similarly, for an IPv6 remote server, only query-source-v6 can be specified.

- -

+

The request-nsid clause determines whether the local server will add a NSID EDNS option to requests sent to the server. This overrides request-nsid set at the view or option level.

- -

+

The send-cookie clause determines whether the local server will add a COOKIE EDNS option to requests sent to the server. This overrides @@ -8810,12 +8210,11 @@ example.com CNAME rpz-tcp-only. determine that COOKIE is not supported by the remote server and not add a COOKIE EDNS option to requests.

-
- -
+
+

statistics-channels Statement Grammar

- 
+
 statistics-channels {
 	inet ( ipv4_address | ipv6_address |
 	    * ) [ port ( integer | * ) ] [
@@ -8823,21 +8222,18 @@ example.com                 CNAME   rpz-tcp-only.
 	    } ];
 };
 

-
- -
+
+

statistics-channels Statement Definition and Usage

- -

+

The statistics-channels statement declares communication channels to be used by system administrators to get access to statistics information of the name server.

- -

+

This statement intends to be flexible to support multiple communication protocols in the future, but currently only HTTP access is supported. @@ -8847,8 +8243,7 @@ example.com CNAME rpz-tcp-only. still accepted even if it is built without the library, but any HTTP access will fail with an error.

- -

+

An inet control channel is a TCP socket listening at the specified ip_port on the specified ip_addr, which can be an IPv4 or IPv6 @@ -8859,14 +8254,12 @@ example.com CNAME rpz-tcp-only. To listen on the IPv6 wildcard address, use an ip_addr of ::.

- -

+

If no port is specified, port 80 is used for HTTP channels. The asterisk "*" cannot be used for ip_port.

- -

+

The attempt of opening a statistics channel is restricted by the optional allow clause. Connections to the statistics channel are permitted based on the @@ -8878,13 +8271,11 @@ example.com CNAME rpz-tcp-only. recommended to restrict the source of connection requests appropriately.

- -

+

If no statistics-channels statement is present, named will not open any communication channels.

- -

+

The statistics are available in various formats and views depending on the URI used to access them. For example, if the statistics channel is configured to listen on 127.0.0.1 @@ -8896,8 +8287,7 @@ example.com CNAME rpz-tcp-only. charts and graphs using the Google Charts API when using a javascript-capable browser.

- -

+

Applications that depend on a particular XML schema can request http://127.0.0.1:8888/xml/v2 for version 2 @@ -8907,8 +8297,7 @@ example.com CNAME rpz-tcp-only. it will respond; if not, it will return a "page not found" error.

- -

+

Broken-out subsets of the statistics can be viewed at http://127.0.0.1:8888/xml/v3/status (server uptime and last reconfiguration time), @@ -8925,8 +8314,7 @@ example.com CNAME rpz-tcp-only. http://127.0.0.1:8888/xml/v3/traffic (traffic sizes).

- -

+

The full set of statistics can also be read in JSON format at http://127.0.0.1:8888/json, with the broken-out subsets at @@ -8945,22 +8333,20 @@ example.com CNAME rpz-tcp-only. http://127.0.0.1:8888/json/v1/traffic (traffic sizes).

-
- -
+
+

trusted-keys Statement Grammar

- 
+
 trusted-keys { string integer integer
     integer quoted_string; ... };
 

-
-
+
+

trusted-keys Statement Definition and Usage

- -

+

The trusted-keys statement defines DNSSEC security roots. DNSSEC is described in the section called “DNSSEC”. A security root is defined when the public key for a non-authoritative zone is known, but @@ -8971,7 +8357,7 @@ example.com CNAME rpz-tcp-only. proven secure. The resolver attempts DNSSEC validation on all DNS data in subdomains of a security root.

-

+

All keys (and corresponding zones) listed in trusted-keys are deemed to exist regardless of what parent zones say. Similarly for all keys listed in @@ -8979,7 +8365,7 @@ example.com CNAME rpz-tcp-only. used to validate the DNSKEY RRset. The parent's DS RRset will not be used.

-

+

The trusted-keys statement can contain multiple key entries, each consisting of the key's domain name, flags, protocol, algorithm, and the Base64 @@ -8988,33 +8374,31 @@ example.com CNAME rpz-tcp-only. in the key data, so the configuration may be split up into multiple lines.

-

+

trusted-keys may be set at the top level of named.conf or within a view. If it is set in both places, they are additive: keys defined at the top level are inherited by all views, but keys defined in a view are only used within that view.

-

+

Validation below specified names can be temporarily disabled by using rndc nta.

-
- -
+
+

managed-keys Statement Grammar

- 
+
 managed-keys { string string integer
     integer integer quoted_string; ... };
 

-
-
+
+

managed-keys Statement Definition and Usage

- -

+

The managed-keys statement, like trusted-keys, defines DNSSEC security roots. The difference is that @@ -9022,7 +8406,7 @@ example.com CNAME rpz-tcp-only. automatically, without intervention from the resolver operator.

-

+

Suppose, for example, that a zone's key-signing key was compromised, and the zone owner had to revoke and replace the key. A resolver which had the old key in a @@ -9032,7 +8416,7 @@ example.com CNAME rpz-tcp-only. continue until the resolver operator had updated the trusted-keys statement with the new key.

-

+

If, however, the zone were listed in a managed-keys statement instead, then the zone owner could add a "stand-by" key to the zone in advance. @@ -9043,7 +8427,7 @@ example.com CNAME rpz-tcp-only. using that key to validate answers, minimizing the damage that the compromised key could do.

-

+

A managed-keys statement contains a list of the keys to be managed, along with information about how the keys are to be initialized for the first time. The only @@ -9054,7 +8438,7 @@ example.com CNAME rpz-tcp-only. allow keys to be initialized by other methods, eliminating this requirement.)

-

+

Consequently, a managed-keys statement appears similar to a trusted-keys, differing in the presence of the second field, containing the keyword @@ -9067,7 +8451,7 @@ example.com CNAME rpz-tcp-only. managed key database and start the RFC 5011 key maintenance process.

-

+

The first time named runs with a managed key configured in named.conf, it fetches the DNSKEY RRset directly from the zone apex, and validates it @@ -9075,7 +8459,7 @@ example.com CNAME rpz-tcp-only. statement. If the DNSKEY RRset is validly signed, then it is used as the basis for a new managed keys database.

-

+

From that point on, whenever named runs, it sees the managed-keys statement, checks to make sure RFC 5011 key maintenance has already been initialized @@ -9084,7 +8468,7 @@ example.com CNAME rpz-tcp-only. statement is not used to validate answers; it has been superseded by the key or keys stored in the managed keys database.

-

+

The next time named runs after a name has been removed from the managed-keys statement, the corresponding @@ -9092,11 +8476,11 @@ example.com CNAME rpz-tcp-only. and RFC 5011 key maintenance will no longer be used for that domain.

-

+

In the current implementation, the managed keys database is stored as a master-format zone file.

-

+

On servers which do not use views, this file is named managed-keys.bind. When views are in use, there will be a separate managed keys database for each @@ -9105,7 +8489,7 @@ example.com CNAME rpz-tcp-only. a hash of the view name), followed by the suffix .mkeys.

-

+

When the key database is changed, the zone is updated. As with any other dynamic zone, changes will be written into a journal file, e.g., @@ -9119,7 +8503,7 @@ example.com CNAME rpz-tcp-only. (For this reason among others, the working directory should be always be writable by named.)

-

+

If the dnssec-validation option is set to auto, named will automatically initialize a managed key for the @@ -9131,12 +8515,10 @@ example.com CNAME rpz-tcp-only. found, the initializing key is also compiled directly into named.

-
- -
+
+

view Statement Grammar

- 
view view_name [ class ] {
     match-clients { address_match_list } ;
     match-destinations { address_match_list } ;
@@ -9145,13 +8527,11 @@ example.com                 CNAME   rpz-tcp-only.
   [ zone_statement ; ... ]
 } ;
- -
-
+
+

view Statement Definition and Usage

- -

+

The view statement is a powerful feature of BIND 9 that lets a name server @@ -9160,8 +8540,7 @@ example.com CNAME rpz-tcp-only. implementing split DNS setups without having to run multiple servers.

- -

+

Each view statement defines a view of the DNS namespace that will be seen by a subset of clients. A client @@ -9189,8 +8568,7 @@ example.com CNAME rpz-tcp-only. a client request will be resolved in the context of the first view that it matches.

- -

+

Zones defined within a view statement will only be accessible to clients that match the view. @@ -9199,8 +8577,7 @@ example.com CNAME rpz-tcp-only. "internal" and "external" clients in a split DNS setup.

- -

+

Many of the options given in the options statement can also be used within a view statement, and then @@ -9213,14 +8590,12 @@ example.com CNAME rpz-tcp-only. view-specific defaults take precedence over those in the options statement.

- -

+

Views are class specific. If no class is given, class IN is assumed. Note that all non-IN views must contain a hint zone, since only the IN class has compiled-in default hints.

- -

+

If there are no view statements in the config file, a default view that matches any client is automatically @@ -9236,12 +8611,10 @@ example.com CNAME rpz-tcp-only. statements must occur inside view statements.

- -

+

Here is an example of a typical split DNS setup implemented using view statements:

- 
view "internal" {
       // This should match our internal networks.
       match-clients { 10.0.0.0/8; };
@@ -9274,13 +8647,11 @@ view "external" {
       };
 };
- -
-
+
+

zone Statement Grammar

- 
 zone string [ class ] {
 	type ( master | primary );
@@ -9447,7 +8818,7 @@ view "external" {
 	forwarders [ port integer ] [ dscp integer ] { ( ipv4_address | ipv6_address ) [ port integer ] [ dscp integer ]; ... };
 	max-records integer;
 	server-addresses { ( ipv4_address | ipv6_address ) [ port integer ]; ... };
-	server-names { quoted_string; ... };
+	server-names { string; ... };
 	zone-statistics ( full | terse | none | boolean );
 };
@@ -9484,16 +8855,14 @@ view "external" { in-view string; }; - -
-
+
+

zone Statement Definition and Usage

- -
+

Zone Types

-

+

The type keyword is required for the zone configuration unless it is an in-view configuration. Its @@ -9507,9 +8876,7 @@ view "external" { static-stub, and stub.

- -
- +
@@ -9831,20 +9198,17 @@ view "external" { -
-
-
- -
+
+
+

Class

- -

+

The zone's name may optionally be followed by a class. If a class is not specified, class IN (for Internet), is assumed. This is correct for the vast majority of cases.

-

+

The hesiod class is named for an information service from MIT's Project Athena. It is @@ -9853,69 +9217,52 @@ view "external" { HS is a synonym for hesiod.

-

+

Another MIT development is Chaosnet, a LAN protocol created in the mid-1970s. Zone data for it can be specified with the CHAOS class.

-
- -
+
+

Zone Options

- -
+
allow-notify
-
-

+

See the description of allow-notify in the section called “Access Control”. -

-
+

allow-query
-
-

+

See the description of allow-query in the section called “Access Control”. -

-
+

allow-query-on
-
-

+

See the description of allow-query-on in the section called “Access Control”. -

-
+

allow-transfer
-
-

+

See the description of allow-transfer in the section called “Access Control”. -

-
+

allow-update
-
-

+

See the description of allow-update in the section called “Access Control”. -

-
+

update-policy
-
-

+

Specifies a "Simple Secure Update" policy. See the section called “Dynamic Update Policies”. -

-
+

allow-update-forwarding
-
-

+

See the description of allow-update-forwarding in the section called “Access Control”. -

-
+

also-notify
-
-

+

Only meaningful if notify is active for this zone. The set of machines that will @@ -9936,11 +9283,9 @@ view "external" { also-notify is not meaningful for stub zones. The default is the empty list. -

-
+

check-names
-
-

+

This option is used to restrict the character set and syntax of certain domain names in master files and/or DNS responses @@ -9948,90 +9293,67 @@ view "external" { network. The default varies according to zone type. For master zones the default is fail. For slave zones the default is warn. It is not implemented for hint zones. -

-
+

check-mx
-
-

+

See the description of check-mx in the section called “Boolean Options”. -

-
+

check-spf
-
-

+

See the description of check-spf in the section called “Boolean Options”. -

-
+

check-wildcard
-
-

+

See the description of check-wildcard in the section called “Boolean Options”. -

-
+

check-integrity
-
-

+

See the description of check-integrity in the section called “Boolean Options”. -

-
+

check-sibling
-
-

+

See the description of check-sibling in the section called “Boolean Options”. -

-
+

zero-no-soa-ttl
-
-

+

See the description of zero-no-soa-ttl in the section called “Boolean Options”. -

-
+

update-check-ksk
-
-

+

See the description of update-check-ksk in the section called “Boolean Options”. -

-
+

dnssec-loadkeys-interval
-
-

+

See the description of dnssec-loadkeys-interval in the section called “options Statement Definition and Usage”. -

-
+

dnssec-update-mode
-
-

+

See the description of dnssec-update-mode in the section called “options Statement Definition and Usage”. -

-
+

dnssec-dnskey-kskonly
-
-

+

See the description of dnssec-dnskey-kskonly in the section called “Boolean Options”. -

-
+

try-tcp-refresh
-
-

+

See the description of try-tcp-refresh in the section called “Boolean Options”. -

-
+

database
-

+

Specify the type of database to be used for storing the zone data. The string following the database keyword is interpreted as a list of whitespace-delimited words. @@ -10042,41 +9364,38 @@ view "external" { specific to the database type.

-

+

The default is "rbt", BIND 9's native in-memory red-black-tree database. This database does not take arguments.

-

+

Other values are possible if additional database drivers have been linked into the server. Some sample drivers are included with the distribution but none are linked in by default.

-
+
dialup
-
-

+

See the description of dialup in the section called “Boolean Options”. -

-
+

delegation-only
-

+

The flag only applies to forward, hint and stub zones. If set to yes, then the zone will also be treated as if it is also a delegation-only type zone.

-

+

See caveats in root-delegation-only.

-
+
file
-
-

+

Set the zone's filename. In master, hint, and redirect zones which do not have masters @@ -10086,30 +9405,24 @@ view "external" { masters defined, zone data is retrieved from another server and saved in this file. This option is not applicable to other zone types. -

-
+

forward
-
-

+

Only meaningful if the zone has a forwarders list. The only value causes the lookup to fail after trying the forwarders and getting no answer, while first would allow a normal lookup to be tried. -

-
+

forwarders
-
-

+

Used to override the list of global forwarders. If it is not specified in a zone of type forward, no forwarding is done for the zone and the global options are not used. -

-
+

ixfr-base
-
-

+

Was used in BIND 8 to specify the name of the transaction log (journal) file for dynamic update @@ -10119,110 +9432,83 @@ view "external" { file by appending ".jnl" to the name of the zone file. -

-
+

ixfr-tmp-file
-
-

+

Was an undocumented option in BIND 8. Ignored in BIND 9. -

-
+

journal
-
-

+

Allow the default journal's filename to be overridden. The default is the zone's filename with ".jnl" appended. This is applicable to master and slave zones. -

-
+

max-journal-size
-
-

+

See the description of max-journal-size in the section called “Server Resource Limits”. -

-
+

max-records
-
-

+

See the description of max-records in the section called “Server Resource Limits”. -

-
+

max-transfer-time-in
-
-

+

See the description of max-transfer-time-in in the section called “Zone Transfers”. -

-
+

max-transfer-idle-in
-
-

+

See the description of max-transfer-idle-in in the section called “Zone Transfers”. -

-
+

max-transfer-time-out
-
-

+

See the description of max-transfer-time-out in the section called “Zone Transfers”. -

-
+

max-transfer-idle-out
-
-

+

See the description of max-transfer-idle-out in the section called “Zone Transfers”. -

-
+

notify
-
-

+

See the description of notify in the section called “Boolean Options”. -

-
+

notify-delay
-
-

+

See the description of notify-delay in the section called “Tuning”. -

-
+

notify-to-soa
-
-

+

See the description of notify-to-soa in the section called “Boolean Options”. -

-
+

pubkey
-
-

+

In BIND 8, this option was intended for specifying a public zone key for verification of signatures in DNSSEC signed zones when they are loaded from disk. BIND 9 does not verify signatures on load and ignores the option. -

-
+

zone-statistics
-
-

+

See the description of zone-statistics in the section called “options Statement Definition and Usage”. -

-
+

server-addresses
-

+

Only meaningful for static-stub zones. This is a list of IP addresses to which queries should be sent in recursive resolution for the @@ -10231,7 +9517,7 @@ view "external" { configure the apex NS RR with associated glue A or AAAA RRs.

-

+

For example, if "example.com" is configured as a static-stub zone with 192.0.2.1 and 2001:db8::1234 in a server-addresses option, @@ -10240,7 +9526,7 @@ view "external" { 

example.com. NS example.com.
 example.com. A 192.0.2.1
 example.com. AAAA 2001:db8::1234
-

+

These records are internally used to resolve names under the static-stub zone. For instance, if the server receives a query for @@ -10248,10 +9534,10 @@ example.com. AAAA 2001:db8::1234 will initiate recursive resolution and send queries to 192.0.2.1 and/or 2001:db8::1234.

-
+
server-names
-

+

Only meaningful for static-stub zones. This is a list of domain names of nameservers that act as authoritative servers of the static-stub @@ -10269,7 +9555,7 @@ example.com. AAAA 2001:db8::1234 "ns.example.net" cannot, and will be rejected by the configuration parser.

-

+

A non empty list for this option will internally configure the apex NS RR with the specified names. For example, if "example.com" is configured as a @@ -10281,7 +9567,7 @@ example.com. AAAA 2001:db8::1234 

example.com. NS ns1.example.net.
 example.com. NS ns2.example.net.
-

+

These records are internally used to resolve names under the static-stub zone. For instance, if the server receives a query for @@ -10291,143 +9577,109 @@ example.com. NS ns2.example.net. "ns2.example.net" to IP addresses, and then send queries to (one or more of) these addresses.

-
+
sig-validity-interval
-
-

+

See the description of sig-validity-interval in the section called “Tuning”. -

-
+

sig-signing-nodes
-
-

+

See the description of sig-signing-nodes in the section called “Tuning”. -

-
+

sig-signing-signatures
-
-

+

See the description of sig-signing-signatures in the section called “Tuning”. -

-
+

sig-signing-type
-
-

+

See the description of sig-signing-type in the section called “Tuning”. -

-
+

transfer-source
-
-

+

See the description of transfer-source in the section called “Zone Transfers”. -

-
+

transfer-source-v6
-
-

+

See the description of transfer-source-v6 in the section called “Zone Transfers”. -

-
+

alt-transfer-source
-
-

+

See the description of alt-transfer-source in the section called “Zone Transfers”. -

-
+

alt-transfer-source-v6
-
-

+

See the description of alt-transfer-source-v6 in the section called “Zone Transfers”. -

-
+

use-alt-transfer-source
-
-

+

See the description of use-alt-transfer-source in the section called “Zone Transfers”. -

-
+

notify-source
-
-

+

See the description of notify-source in the section called “Zone Transfers”. -

-
+

notify-source-v6
-
-

+

See the description of notify-source-v6 in the section called “Zone Transfers”. -

-
+

min-refresh-time, max-refresh-time, min-retry-time, max-retry-time
-
-

+

See the description in the section called “Tuning”. -

-
+

ixfr-from-differences
-
-

+

See the description of ixfr-from-differences in the section called “Boolean Options”. (Note that the ixfr-from-differences master and slave choices are not available at the zone level.) -

-
+

key-directory
-
-

+

See the description of key-directory in the section called “options Statement Definition and Usage”. -

-
+

auto-dnssec
-
-

+

See the description of auto-dnssec in the section called “options Statement Definition and Usage”. -

-
+

serial-update-method
-
-

+

See the description of serial-update-method in the section called “options Statement Definition and Usage”. -

-
+

inline-signing
-
-

+

If yes, this enables "bump in the wire" signing of a zone, where a unsigned zone is transferred in or loaded from disk and a signed version of the zone is served, with possibly, a different serial number. This behavior is disabled by default. -

-
+

mirror
-

+

If set to yes, this causes the zone to become a mirror zone. A mirror zone is a secondary zone whose data @@ -10435,7 +9687,7 @@ example.com. NS ns2.example.net. used in answers. The default is no.

-

+

A mirror zone's contents are validated during the transfer process, and again when the zone file is loaded from disk when named is restarted. If validation @@ -10444,7 +9696,7 @@ example.com. NS ns2.example.net. version has expired, traditional DNS recursion will be used to look up the answers instead.

-

+

For validation to succeed, a key-signing key (KSK) for the zone must be configured as a trust anchor in named.conf: @@ -10458,7 +9710,7 @@ example.com. NS ns2.example.net. exceptions that the AA bit ("authoritative answer") is not set, and the AD bit ("authenticated data") is.

-

+

Though this option can be used for other zones, it is intended to be used to set up a fast local copy of the root zone, as described in RFC 7706. @@ -10483,56 +9735,46 @@ example.com. NS ns2.example.net. 2620:0:2d0:202::132; # xfr.lax.dns.icann.org }; }; -

+
multi-master
-
-

+

See the description of multi-master in the section called “Boolean Options”. -

-
+

masterfile-format
-
-

+

See the description of masterfile-format in the section called “Tuning”. -

-
+

max-zone-ttl
-
-

+

See the description of max-zone-ttl in the section called “options Statement Definition and Usage”. -

-
+

dnssec-secure-to-insecure
-
-

+

See the description of dnssec-secure-to-insecure in the section called “Boolean Options”. -

-
+

- -
-
+
+

Dynamic Update Policies

- -

BIND 9 supports two alternative +

BIND 9 supports two alternative methods of granting clients the right to perform dynamic updates to a zone, configured by the allow-update and update-policy option, respectively.

-

+

The allow-update clause is a simple access control list. Any client that matches the ACL is granted permission to update any record in the zone.

-

+

The update-policy clause allows more fine-grained control over what updates are allowed. It specifies a set of rules, in which each rule @@ -10545,7 +9787,7 @@ example.com. NS ns2.example.net. to specify update permissions based on client source address.

-

+

update-policy rules are only meaningful for zones of type master, and are not allowed in any other zone type. @@ -10553,7 +9795,7 @@ example.com. NS ns2.example.net. allow-update and update-policy at the same time.

-

+

A pre-defined update-policy rule can be switched on with the command update-policy local;. @@ -10576,35 +9818,30 @@ example.com. NS ns2.example.net. within the zone. Assuming the key name is "local-ddns", this policy is equivalent to:

- - 
update-policy { grant local-ddns zonesub any; };
+
update-policy { grant local-ddns zonesub any; };
             

-
-            

+

               ...with the additional restriction that only clients
               connecting from the local system will be permitted to send
               updates.
             

-            

+

               Note that only one session key is generated by
               named; all zones configured to use
               update-policy local will accept the same key.
             

-            

+

               The command nsupdate -l implements this
               feature, sending requests to localhost and signing them using
               the key retrieved from the session key file.
             

-
-            

+

               Other rule definitions look like this:
             

-
 
 ( grant | deny ) identity ruletype [ name ] [ types ]
 

-
-            

+

               Each rule grants or denies privileges.  Rules are checked
               in the order in which they are specified in the
               update-policy statement. Once a message
@@ -10614,7 +9851,7 @@ example.com. NS ns2.example.net.
               ruletype field, and the interpretation
               of other fields varies depending on the rule type.
             

-            

+

               In general, a rule is matched when the
               key that signed an update request matches the
               identity field, the name of the record
@@ -10624,7 +9861,7 @@ example.com. NS ns2.example.net.
               types field. Details for each rule type
               are described below.
             

-            

+

               The identity field must be set to
               a fully-qualified domain name.  In most cases, this
               represensts the name of the TSIG or SIG(0) key that must be
@@ -10634,17 +9871,17 @@ example.com. NS ns2.example.net.
               has been used to create a shared secret, the identity of
               the key used to authenticate the TKEY exchange will be
               used as the identity of the shared secret.  Some rule types
-              use indentities matching the client's Kerberos principal
+              use identities matching the client's Kerberos principal
               (e.g, "host/machine@REALM") or
               Windows realm (machine$@REALM).
             

-            

+

               The name field also specifies
               a fully-qualified domain name. This often
               represents the name of the record to be updated.
               Interpretation of this field is dependent on rule type.
             

-            

+

               If no types are explicitly specified,
               then a rule matches all types except RRSIG, NS, SOA, NSEC
               and NSEC3. Types may be specified by name, including
@@ -10653,7 +9890,7 @@ example.com. NS ns2.example.net.
               is made to delete all records associated with a name,
               the rules are checked for each existing record type.
             

-            

+

               The ruletype field has 13
               values:
               name, subdomain,
@@ -10665,8 +9902,7 @@ example.com. NS ns2.example.net.
               tcp-self, 6to4-self,
               zonesub, and external.
             

-            

-              
+
@@ -10804,12 +10040,26 @@ example.com. NS ns2.example.net.
                     
@@ -10821,13 +10071,32 @@ example.com. NS ns2.example.net.
                     
@@ -10838,12 +10107,32 @@ example.com. NS ns2.example.net.
                     
@@ -10855,13 +10144,11 @@ example.com. NS ns2.example.net.
                     
@@ -10978,15 +10265,12 @@ example.com. NS ns2.example.net.
                     
-

 
 
 

 

                       

-                        This rule takes a Windows machine principal
-                        (machine$@REALM) for machine in REALM and
-                        and converts it machine.realm allowing the machine
-                        to update machine.realm.  The REALM to be matched
-                        is specified in the identity
-                        field.  The name field should be set to "."
+                        When a client sends an UPDATE using a Windows
+                        machine principal (for example, 'machine$@REALM'),
+                        this rule allows records with the absolute name
+                        of 'machine.REALM' to be updated.
+                      

+                      

+                        The realm to be matched is specified in the
+                        identity field.
+                      

+                      

+                        The name field has
+                        no effect on this rule; it should be set to "."
+                        as a placeholder.
+                      

+                      

+                        For example,
+                        grant EXAMPLE.COM ms-self . A AAAA
+                        allows any machine with a valid principal in
+                        the realm EXAMPLE.COM to update
+                        its own address records.
                       

                     		
 

 

                       

-                        This rule takes a Windows machine principal
-                        (machine$@REALM) for machine in REALM and
-                        converts it to machine.realm allowing the machine
-                        to update subdomains of machine.realm.  The REALM
-                        to be matched is specified in the
+                        When a client sends an UPDATE using a Windows
+                        machine principal (for example, 'machine$@REALM'),
+                        this rule allows any machine in the specified
+                        realm to update any record in the zone or in a
+                        specified subdomain of the zone.
+                      

+                      

+                        The realm to be matched is specified in the
                         identity field.
                       

+                      

+                        The name field
+                        specifies the subdomain that may be updated.
+                        If set to "." (or any other name at or above
+                        the zone apex), any name in the zone can be
+                        updated.
+                      

+                      

+                        For example, if update-policy
+                        for the zone "example.com" includes
+                        grant EXAMPLE.COM ms-subdomain hosts.example.com. A AAAA,
+                        any machine with a valid principal in
+                        the realm EXAMPLE.COM will
+                        be able to update address records at or below
+                        "hosts.example.com".
+                      

                     		
 

 

 
                       

-                        This rule takes a Kerberos machine principal
-                        (host/machine@REALM) for machine in REALM and
-                        and converts it machine.realm allowing the machine
-                        to update machine.realm.  The REALM to be matched
-                        is specified in the identity
-                        field. The name field should be set to "."
+                        When a client sends an UPDATE using a
+                        Kerberos machine principal (for example,
+                        'host/machine@REALM'), this rule allows
+                        records with the absolute name of 'machine'
+                        to be updated provided it has been authenticated
+                        by REALM.  This is similar but not identical
+                        to ms-self due to the
+                        'machine' part of the Kerberos principal
+                        being an absolute name instead of a unqualified
+                        name.
+                      

+                      

+                        The realm to be matched is specified in the
+                        identity field.
+                      

+                      

+                        The name field has
+                        no effect on this rule; it should be set to "."
+                        as a placeholder.
+                      

+                      

+                        For example,
+                        grant EXAMPLE.COM krb5-self . A AAAA
+                        allows any machine with a valid principal in
+                        the realm EXAMPLE.COM to update
+                        its own address records.
                       

                     		
 

 

                       

-                        This rule takes a Kerberos machine principal
-                        (host/machine@REALM) for machine in REALM and
-                        converts it to machine.realm allowing the machine
-                        to update subdomains of machine.realm.  The REALM
-                        to be matched is specified in the
-                        identity field. The
-                        name field should be set to "."
+                        This rule is identical to
+                        ms-subdomain, except that it works
+                        with Kerberos machine principals (i.e.,
+                        'host/machine@REALM') rather than Windows machine
+                        principals.
                       

                     		
 

 
 

-            

-
- -
+
+
+

Multiple views

- -

+

When multiple views are in use, a zone may be referenced by more than one of them. Often, the views will contain different zones with the same name, allowing @@ -10997,7 +10281,7 @@ example.com. NS ns2.example.net. way to do this: it allows a view to reference a zone that was defined in a previously configured view. Example:

- 
+
 view internal {
     match-clients { 10/8; };
 
@@ -11015,11 +10299,11 @@ view external {
     };
 };
             

-            

+

               An in-view option cannot refer to a view
               that is configured later in the configuration file.
             

-            

+

               A zone statement which uses the
               in-view option may not use any other
               options with the exception of forward
@@ -11027,45 +10311,41 @@ view external {
               the behavior of the containing view, rather than changing
               the zone object itself.)
             

-            

+

               Zone level acls (e.g. allow-query, allow-transfer) and
               other configuration details of the zone are all set
               in the view the referenced zone is defined in.  Care
               need to be taken to ensure that acls are wide enough
               for all views referencing the zone.
             

-            

+

               An in-view zone cannot be used as a
               response policy zone.
             

-            

+

               An in-view zone is not intended to reference
               a forward zone.
             

-
- -
-
-
+
+
+
+

Zone File

- -
+

Types of Resource Records and When to Use Them

- -

+

This section, largely borrowed from RFC 1034, describes the concept of a Resource Record (RR) and explains when each is used. Since the publication of RFC 1034, several new RRs have been identified and implemented in the DNS. These are also included.

-
+

Resource Records

- -

+

A domain name identifies a node. Each node has a set of resource information, which may be empty. The set of resource information associated with a particular name is composed of @@ -11075,12 +10355,10 @@ view external { permitted for optimization purposes, for example, to specify that a particular nearby server be tried first. See the section called “The sortlist Statement” and the section called “RRset Ordering”.

- -

+

The components of a Resource Record are:

-
- +
@@ -11155,13 +10433,11 @@ view external { -
-
-

+

+

The following are types of valid RRs:

-
- +
@@ -12179,14 +11455,12 @@ view external { -
-
-

+

+

The following classes of resource records are currently valid in the DNS:

-
- +
@@ -12239,10 +11513,8 @@ view external { -
-
- -

+

+

The owner name is often implicit, rather than forming an integral part of the RR. For example, many name servers internally form @@ -12253,7 +11525,7 @@ view external { that fits the needs of the resource being described.

-

+

The meaning of the TTL field is a time limit on how long an RR can be kept in a cache. This limit does not apply to authoritative @@ -12273,18 +11545,17 @@ view external { following the change.

-

+

The data in the RDATA section of RRs is carried as a combination of binary strings and domain names. The domain names are frequently used as "pointers" to other data in the DNS.

-
-
+
+

Textual expression of RRs

- -

+

RRs are represented in binary form in the packets of the DNS protocol, and are usually represented in highly encoded form when @@ -12297,13 +11568,13 @@ view external { possible using parentheses.

-

+

The start of the line gives the owner of the RR. If a line begins with a blank, then the owner is assumed to be the same as that of the previous RR. Blank lines are often included for readability.

-

+

Following the owner, we list the TTL, type, and class of the RR. Class and type use the mnemonics defined above, and TTL is an integer before the type field. In order to avoid ambiguity @@ -12314,15 +11585,14 @@ view external { values are often omitted from examples in the interests of clarity.

-

+

The resource data or RDATA section of the RR are given using knowledge of the typical representation for the data.

-

+

For example, we might show the RRs carried in a message as:

-
- +
@@ -12426,23 +11696,21 @@ view external { -
-
-

+

+

The MX RRs have an RDATA section which consists of a 16-bit number followed by a domain name. The address RRs use a standard IP address format to contain a 32-bit internet address.

-

+

The above example shows six RRs, with two RRs at each of three domain names.

-

+

Similarly we might see:

-
- +
@@ -12480,20 +11748,17 @@ view external { -
-
-

+

+

This example shows two addresses for XX.LCS.MIT.EDU, each of a different class.

-
-
- -
+
+
+

Discussion of MX Records

- -

+

As described above, domain servers store information as a series of resource records, each of which contains a particular piece of information about a given domain name (which is usually, @@ -12502,8 +11767,7 @@ view external { and stored with some additional type information to help systems determine when the RR is relevant.

- -

+

MX records are used to control delivery of email. The data specified in the record is a priority and a domain name. The priority @@ -12520,7 +11784,7 @@ view external { It must have an associated address record (A or AAAA) — CNAME is not sufficient.

-

+

For a given domain, if there is both a CNAME record and an MX record, the MX record is in error, and will be ignored. Instead, @@ -12529,8 +11793,7 @@ view external { pointed to by the CNAME. For example:

-
- +
@@ -12667,20 +11930,18 @@ view external { -
-
+

Mail delivery will be attempted to mail.example.com and mail2.example.com (in any order), and if neither of those succeed, delivery to mail.backup.org will be attempted.

-
-
+
+

Setting TTLs

- -

+

The time-to-live of the RR field is a 32-bit integer represented in units of seconds, and is primarily used by resolvers when they cache RRs. The TTL describes how long a RR can be cached before it @@ -12688,8 +11949,7 @@ view external { currently used in a zone file.

-
- +
@@ -12744,18 +12004,16 @@ view external { -
-
-

+

+

All of these TTLs default to units of seconds, though units can be explicitly specified, for example, 1h30m.

-
-
+
+

Inverse Mapping in IPv4

- -

+

Reverse name resolution (that is, translation from IP address to name) is achieved by means of the in-addr.arpa domain and PTR records. Entries in the in-addr.arpa domain are made in @@ -12770,8 +12028,7 @@ view external { PTR records if the machine has more than one name. For example, in the [example.com] domain:

-
- +
@@ -12802,24 +12059,22 @@ view external { -
-
-
+
+

Note

-

+

The $ORIGIN lines in the examples are for providing context to the examples only — they do not necessarily appear in the actual usage. They are only used here to indicate that the example is relative to the listed origin.

-
-
-
+
+
+

Other Zone File Directives

- -

+

The Master File Format was initially defined in RFC 1035 and has subsequently been extended. While the Master File Format itself @@ -12827,32 +12082,30 @@ view external { same class.

-

+

Master File Directives include $ORIGIN, $INCLUDE, and $TTL.

-
+

The @ (at-sign)

- -

+

When used in the label (or name) field, the asperand or at-sign (@) symbol represents the current origin. At the start of the zone file, it is the <zone_name> (followed by trailing dot).

-
-
+
+

The $ORIGIN Directive

- -

+

Syntax: $ORIGIN domain-name [comment]

-

$ORIGIN +

$ORIGIN sets the domain name that will be appended to any unqualified records. When a zone is first read in there is an implicit $ORIGIN @@ -12862,47 +12115,42 @@ view external { the domain specified in the $ORIGIN argument if it is not absolute.

- 
 $ORIGIN example.com.
 WWW     CNAME   MAIN-SERVER
- -

+

is equivalent to

- 
 WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
- -
-
+
+

The $INCLUDE Directive

- -

+

Syntax: $INCLUDE filename [ origin ] [ comment ]

-

+

Read and process the file filename as if it were included into the file at this point. If origin is specified the file is processed with $ORIGIN set to that value, otherwise the current $ORIGIN is used.

-

+

The origin and the current domain name revert to the values they had prior to the $INCLUDE once the file has been read.

-
+

Note

-

+

RFC 1035 specifies that the current origin should be restored after an $INCLUDE, but it is silent @@ -12912,33 +12160,31 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. This could be construed as a deviation from RFC 1035, a feature, or both.

-
-
-
+
+
+

The $TTL Directive

- -

+

Syntax: $TTL default-ttl [ comment ]

-

+

Set the default Time To Live (TTL) for subsequent records with undefined TTLs. Valid TTLs are of the range 0-2147483647 seconds.

-

$TTL +

$TTL is defined in RFC 2308.

-
-
-
+
+
+

BIND Master File Extension: the $GENERATE Directive

- -

+

Syntax: $GENERATE range lhs @@ -12948,7 +12194,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. rhs [comment]

-

$GENERATE +

$GENERATE is used to create a series of resource records that only differ from each other by an iterator. $GENERATE can be used to @@ -12956,15 +12202,12 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. sub /24 reverse delegations described in RFC 2317: Classless IN-ADDR.ARPA delegation.

- 
$ORIGIN 0.0.192.IN-ADDR.ARPA.
 $GENERATE 1-2 @ NS SERVER$.EXAMPLE.
 $GENERATE 1-127 $ CNAME $.0
- -

+

is equivalent to

- 
0.0.0.192.IN-ADDR.ARPA. NS SERVER1.EXAMPLE.
 0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE.
 1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA.
@@ -12972,22 +12215,18 @@ $GENERATE 1-127 $ CNAME $.0
... 127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA. - -

+

Generate a set of A and MX records. Note the MX's right hand side is a quoted string. The quotes will be stripped when the right hand side is processed.

- 
 $ORIGIN EXAMPLE.
 $GENERATE 1-127 HOST-$ A 1.2.3.$
 $GENERATE 1-127 HOST-$ MX "0 ."
- -

+

is equivalent to

- 
HOST-1.EXAMPLE.   A  1.2.3.1
 HOST-1.EXAMPLE.   MX 0 .
 HOST-2.EXAMPLE.   A  1.2.3.2
@@ -12998,9 +12237,7 @@ HOST-3.EXAMPLE.   MX 0 .
 HOST-127.EXAMPLE. A  1.2.3.127
 HOST-127.EXAMPLE. MX 0 .
- -
- +
@@ -13128,33 +12365,30 @@ HOST-127.EXAMPLE. MX 0 . -
-
-

+

+

The $GENERATE directive is a BIND extension and not part of the standard zone file format.

-

+

BIND 8 did not support the optional TTL and CLASS fields.

-
- -
+
+

Additional File Formats

- -

+

In addition to the standard textual format, BIND 9 supports the ability to read or dump to zone files in other formats.

-

+

The raw format is a binary representation of zone data in a manner similar to that used in zone transfers. Since it does not require parsing text, load time is significantly reduced.

-

+

An even faster alternative is the map format, which is an image of a BIND 9 in-memory zone database; it is capable of being loaded @@ -13162,7 +12396,7 @@ HOST-127.EXAMPLE. MX 0 . function; the zone can begin serving queries almost immediately.

-

+

For a primary server, a zone file in raw or map format is expected to be generated from a textual zone @@ -13173,7 +12407,7 @@ HOST-127.EXAMPLE. MX 0 . named dumps the zone contents after zone transfer or when applying prior updates.

-

+

If a zone file in a binary format needs manual modification, it first must be converted to a textual form by the named-compilezone command. All @@ -13181,7 +12415,7 @@ HOST-127.EXAMPLE. MX 0 . should then be converted to the binary form by the named-compilezone command again.

-

+

Note that map format is extremely architecture-specific. A map file cannot be used on a system @@ -13198,14 +12432,12 @@ HOST-127.EXAMPLE. MX 0 . portable backup of such a file, conversion to text format is recommended.

-
-
- -
+
+
+

BIND9 Statistics

- -

+

BIND 9 maintains lots of statistics information and provides several interfaces for users to get access to the statistics. @@ -13214,14 +12446,11 @@ HOST-127.EXAMPLE. MX 0 . are meaningful in BIND 9, and other information that is considered useful.

- -

+

The statistics information is categorized into the following sections.

- -
- +
@@ -13320,10 +12549,8 @@ HOST-127.EXAMPLE. MX 0 . -
-
- -

+

+

A subset of Name Server Statistics is collected and shown per zone for which the server has the authority when zone-statistics is set to @@ -13333,13 +12560,11 @@ HOST-127.EXAMPLE. MX 0 . Usage” for further details.

- -

+

These statistics counters are shown with their zone and view names. The view name is omitted when the server is not configured with explicit views.

- -

+

There are currently two user interfaces to get access to the statistics. One is in the plain text format dumped to the file specified @@ -13349,18 +12574,16 @@ HOST-127.EXAMPLE. MX 0 . is specified in the configuration file (see the section called “statistics-channels Statement Grammar”.)

- -
+

The Statistics File

- -

+

The text format statistics dump begins with a line, like:

-

+

+++ Statistics Dump +++ (973798949)

-

+

The number in parentheses is a standard Unix-style timestamp, measured as seconds since January 1, 1970. @@ -13369,33 +12592,28 @@ HOST-127.EXAMPLE. MX 0 . as described above. Each section begins with a line, like:

- -

+

++ Name Server Statistics ++

- -

+

Each section consists of lines, each containing the statistics counter value followed by its textual description. See below for available counters. For brevity, counters that have a value of 0 are not shown in the statistics file.

- -

+

The statistics dump ends with the line where the number is identical to the number in the beginning line; for example:

-

+

--- Statistics Dump --- (973798949)

-
- -
+
+

Statistics Counters

- -

+

The following tables summarize statistics counters that BIND 9 provides. For each row of the tables, the leftmost column is the @@ -13411,13 +12629,10 @@ HOST-127.EXAMPLE. MX 0 . it gives the corresponding counter name of the BIND 8 statistics, if applicable.

- -
+

Name Server Statistics Counters

- -
- +
@@ -14035,16 +13250,12 @@ HOST-127.EXAMPLE. MX 0 . -
-
-
- -
+
+
+

Zone Maintenance Statistics Counters

- -
- +
@@ -14193,16 +13404,12 @@ HOST-127.EXAMPLE. MX 0 . -
-
-
- -
+
+
+

Resolver Statistics Counters

- -
- +
@@ -14580,16 +13787,12 @@ HOST-127.EXAMPLE. MX 0 . -
-
- -
- -
+
+
+

Socket I/O Statistics Counters

- -

+

Socket I/O statistics counters are defined per socket types, which are UDP4 (UDP/IPv4), @@ -14604,9 +13807,7 @@ HOST-127.EXAMPLE. MX 0 . Not all counters are available for all socket types; exceptions are noted in the description field.

- -
- +
@@ -14741,58 +13942,45 @@ HOST-127.EXAMPLE. MX 0 . -
-
-
- -
+
+
+

Compatibility with BIND 8 Counters

- -

+

Most statistics counters that were available in BIND 8 are also supported in BIND 9 as shown in the above tables. Here are notes about other counters that do not appear in these tables.

- -
+
RFwdR,SFwdR
-
-

+

These counters are not supported because BIND 9 does not adopt the notion of forwarding as BIND 8 did. -

-
+

RAXFR
-
-

+

This counter is accessible in the Incoming Queries section. -

-
+

RIQ
-
-

+

This counter is accessible in the Incoming Requests section. -

-
+

ROpts
-
-

+

This counter is not supported because BIND 9 does not care about IP options in the first place. -

-
+

-
-
-
- - + + + +
@@ -14810,6 +13998,6 @@ HOST-127.EXAMPLE. MX 0 .
-

BIND 9.13.2 (Development Release)

+

BIND 9.13.3-dev (Development Release)

diff --git a/doc/arm/Bv9ARM.ch06.html b/doc/arm/Bv9ARM.ch06.html index 3b584347bd001f4b85e486ded9f8ced768337de1..c271922f3aebe2a98a26001b336368e7ee11b5be 100644 --- a/doc/arm/Bv9ARM.ch06.html +++ b/doc/arm/Bv9ARM.ch06.html @@ -10,7 +10,7 @@ Chapter 6. BIND 9 Security Considerations - + @@ -45,12 +45,10 @@
Dynamic Update Security
- -
+

Access Control Lists

- -

+

Access Control Lists (ACLs) are address match lists that you can set up and nickname for future use in allow-notify, allow-query, @@ -58,27 +56,26 @@ blackhole, allow-transfer, match-clients, etc.

-

+

Using ACLs allows you to have finer control over who can access your name server, without cluttering up your config files with huge lists of IP addresses.

-

+

It is a good idea to use ACLs, and to control access to your server. Limiting access to your server by outside parties can help prevent spoofing and denial of service (DoS) attacks against your server.

-

+

ACLs match clients on the basis of up to three characteristics: 1) The client's IP address; 2) the TSIG or SIG(0) key that was used to sign the request, if any; and 3) an address prefix encoded in an EDNS Client Subnet option, if any.

-

+

Here is an example of ACLs based on client addresses:

- 
 // Set up an ACL named "bogusnets" that will block
 // RFC1918 space and some reserved space, which is
@@ -107,33 +104,32 @@ zone "example.com" {
   allow-query { any; };
 };
- -

+

This allows authoritative queries for "example.com" from any address, but recursive queries only from the networks specified in "our-nets", and no queries at all from the networks specified in "bogusnets".

-

+

In addition to network addresses and prefixes, which are matched against the source address of the DNS request, ACLs may include key elements, which specify the name of a TSIG or SIG(0) key.

-

+

When BIND 9 is built with GeoIP support, ACLs can also be used for geographic access restrictions. This is done by specifying an ACL element of the form: geoip [db database] field value

-

+

The field indicates which field to search for a match. Available fields are "country", "region", "city", "continent", "postal" (postal code), "metro" (metro code), "area" (area code), "tz" (timezone), "isp", "org", "asnum", "domain" and "netspeed".

-

+

value is the value to search for within the database. A string may be quoted if it contains spaces or other special characters. If this is @@ -149,7 +145,7 @@ zone "example.com" { standard two-letter state or province abbreviation; otherwise it is the full name of the state or province.

-

+

The database field indicates which GeoIP database to search for a match. In most cases this is unnecessary, because most search fields can only be found in @@ -164,10 +160,10 @@ zone "example.com" { database if it is installed, or the "region" database if it is installed, or the "country" database, in that order.

-

+

Some example GeoIP ACLs:

- 
geoip country US;
+
geoip country US;
 geoip country JAP;
 geoip db country country Canada;
 geoip db region region WA;
@@ -177,8 +173,7 @@ geoip postal 95062;
 geoip tz "America/Los_Angeles";
 geoip org "Internet Systems Consortium";
 

-
-        

+

           ACLs use a "first-match" logic rather than "best-match":
           if an address prefix matches an ACL element, then that ACL
           is considered to have matched even if a later element would
@@ -188,7 +183,7 @@ geoip org "Internet Systems Consortium";
           indicated that the query should be accepted, and the second
           element is ignored.
         

-        

+

           When using "nested" ACLs (that is, ACLs included or referenced
           within other ACLs), a negative match of a nested ACL will
           the containing ACL to continue looking for matches.  This
@@ -198,10 +193,10 @@ geoip org "Internet Systems Consortium";
           it originates from a particular network and
           only when it is signed with a particular key, use:
         

-        
+
 allow-query { !{ !10/8; any; }; key example; };
 

-        

+

           Within the nested ACL, any address that is
           not in the 10/8 network prefix will
           be rejected, and this will terminate processing of the
@@ -213,14 +208,12 @@ allow-query { !{ !10/8; any; }; key example; };
           will only matches when both conditions
           are true.
         

-
- -
+
+

Chroot and Setuid

- -

+

On UNIX servers, it is possible to run BIND in a chrooted environment (using the chroot() function) by specifying @@ -229,25 +222,23 @@ allow-query { !{ !10/8; any; }; key example; }; BIND in a "sandbox", which will limit the damage done if a server is compromised.

-

+

Another useful feature in the UNIX version of BIND is the ability to run the daemon as an unprivileged user ( -u user ). We suggest running as an unprivileged user when using the chroot feature.

-

+

Here is an example command line to load BIND in a chroot sandbox, /var/named, and to run named setuid to user 202:

-

+

/usr/local/sbin/named -u 202 -t /var/named

- -
+

The chroot Environment

- -

+

In order for a chroot environment to work properly in a particular directory (for example, /var/named), you will need to set @@ -259,7 +250,7 @@ allow-query { !{ !10/8; any; }; key example; }; options like directory and pid-file to account for this.

-

+

Unlike with earlier versions of BIND, you typically will not need to compile named statically nor install shared libraries under the new root. @@ -270,13 +261,11 @@ allow-query { !{ !10/8; any; }; key example; }; /dev/log, and /etc/localtime.

-
- -
+
+

Using the setuid Function

- -

+

Prior to running the named daemon, use the touch utility (to change file @@ -287,7 +276,7 @@ allow-query { !{ !10/8; any; }; key example; }; to which you want BIND to write.

-
+

Note

If the named daemon is running as an @@ -295,14 +284,12 @@ allow-query { !{ !10/8; any; }; key example; }; ports if the server is reloaded.

-
-
- -
+
+
+

Dynamic Update Security

- -

+

Access to the dynamic update facility should be strictly limited. In earlier versions of BIND, the only way to do this was @@ -322,8 +309,7 @@ allow-query { !{ !10/8; any; }; key example; }; forward it to the master with its own source IP address causing the master to approve it without question.

- -

+

For these reasons, we strongly recommend that updates be cryptographically authenticated by means of transaction signatures (TSIG). That is, the allow-update @@ -332,8 +318,7 @@ allow-query { !{ !10/8; any; }; key example; }; prefixes. Alternatively, the new update-policy option can be used.

- -

+

Some sites choose to keep all dynamically-updated DNS data in a subdomain and delegate that subdomain to a separate zone. This way, the top-level zone containing critical data such as the IP @@ -341,9 +326,8 @@ allow-query { !{ !10/8; any; }; key example; }; of public web and mail servers need not allow dynamic update at all.

- -
-
+
+
@@ -361,6 +345,6 @@ allow-query { !{ !10/8; any; }; key example; };
-

BIND 9.13.2 (Development Release)

+

BIND 9.13.3-dev (Development Release)

diff --git a/doc/arm/Bv9ARM.ch07.html b/doc/arm/Bv9ARM.ch07.html index 877878f98b9dfa091cdce0dafdf363dd7736defd..079a5c5efe4452cd485949f8f35fa0cae3fd378f 100644 --- a/doc/arm/Bv9ARM.ch07.html +++ b/doc/arm/Bv9ARM.ch07.html @@ -10,7 +10,7 @@ Chapter 7. Troubleshooting - + @@ -37,35 +37,85 @@

Table of Contents

Common Problems
-
It's not working; how can I figure out what's wrong?
+
+
It's not working; how can I figure out what's wrong?
+
EDNS compliance issues
+
Incrementing and Changing the Serial Number
Where Can I Get Help?
- -
+

Common Problems

- -
+

It's not working; how can I figure out what's wrong?

- -

+

The best solution to solving installation and configuration issues is to take preventative measures by setting up logging files beforehand. The log files provide a source of hints and information that can be used to figure out what went wrong and how to fix the problem.

- -
-
-
+
+
+

+EDNS compliance issues

+

+ EDNS (Extended DNS) is a standard that was first specified + in 1999. It is required for DNSSEC validation, DNS COOKIE + options, and other features. There are broken and outdated + DNS servers and firewalls still in use which misbehave when + queried with EDNS; for example, they may drop EDNS queries + rather than replying with FORMERR. BIND and other recursive + name servers have traditionally employed workarounds in this + situation, retrying queries in different ways and eventually + falling back to plain DNS queries without EDNS. +

+

+ Such workarounds cause unnecessary resolution delays, + increase code complexity, and prevent deployment of new DNS + features. As of February 2019, all major DNS software vendors + have agreed to remove these workarounds; see + https://dnsflagday.net + for further details. This change was implemented in BIND + as of release 9.14.0. +

+

+ As a result, some domains may be non-resolvable without manual + intervention. In these cases, resolution can be restored by + adding server clauses for the offending + servers, specifying edns no or + send-cookie no, depending on the specific + noncompliance. +

+

+ To determine which server clause to use, + run the following commands to send queries to the authoritative + servers for the broken domain: +

+


+            dig soa <zone> @<server> +dnssec
+            dig soa <zone> @<server> +dnssec +nocookie
+            dig soa <zone> @<server> +noedns
+  

+

+ If the first command fails but the second succeeds, the + server most likely needs send-cookie no. + If the first two fail but the third succeeds, then the server + needs EDNS to be fully disabled with edns no. +

+

+ Please contact the administrators of noncompliant domains + and encourage them to upgrade their broken DNS servers. +

+
+
+

Incrementing and Changing the Serial Number

- -

+

Zone serial numbers are just numbers — they aren't date related. A lot of people set them to a number that represents a date, usually of the form YYYYMMDDRR. @@ -77,26 +127,22 @@ lower than the serial number on the master, the slave server will attempt to update its copy of the zone.

- -

+

Setting the serial number to a lower number on the master server than the slave server means that the slave will not perform updates to its copy of the zone.

- -

+

The solution to this is to add 2147483647 (2^31-1) to the number, reload the zone and make sure all slaves have updated to the new zone serial number, then reset the number to what you want it to be, and reload the zone again.

- -
-
+
+

Where Can I Get Help?

- -

+

The Internet Systems Consortium (ISC) offers a wide range of support and service agreements for BIND and DHCP servers. Four @@ -109,16 +155,15 @@ fix announcements to remote support. It also includes training in BIND and DHCP.

- -

+

To discuss arrangements for support, contact info@isc.org or visit the ISC web page at http://www.isc.org/services/support/ to read more.

-
-
+ +
@@ -136,6 +181,6 @@
-

BIND 9.13.2 (Development Release)

+

BIND 9.13.3-dev (Development Release)

diff --git a/doc/arm/Bv9ARM.ch08.html b/doc/arm/Bv9ARM.ch08.html index bb6a491f4afeebcfe558156971afcd03a856b09c..152db83af8d918150038a11ca6ac9544b0501707 100644 --- a/doc/arm/Bv9ARM.ch08.html +++ b/doc/arm/Bv9ARM.ch08.html @@ -10,7 +10,7 @@ Appendix A. Release Notes - + @@ -36,7 +36,7 @@

Table of Contents

-
Release Notes for BIND Version 9.13.2
+
Release Notes for BIND Version 9.13.3-dev
Introduction
Note on Version Numbering
@@ -52,31 +52,29 @@
-
+

-Release Notes for BIND Version 9.13.2

- -
+Release Notes for BIND Version 9.13.3-dev
+

Introduction

-

+

BIND 9.13 is an unstable development release of BIND. This document summarizes new features and functional changes that have been introduced on this branch. With each development release leading up to the stable BIND 9.14 release, this document will be updated with additional features added and bugs fixed.

-
- -
+
+

Note on Version Numbering

-

+

Prior to BIND 9.13, new feature development releases were tagged as "alpha" and "beta", leading up to the first stable release for a given development branch, which always ended in ".0".

-

+

Now, however, BIND has adopted the "odd-unstable/even-stable" release numbering convention. There will be no "alpha" or "beta" releases in the 9.13 branch, only increasing version numbers. @@ -84,46 +82,47 @@ 9.13.0a2, 9.13.0b1, and so on, will instead be called 9.13.0, 9.13.1, 9.13.2, etc.

-

+

The first stable release from this development branch will be renamed as 9.14.0. Thereafter, maintenance releases will continue on the 9.14 branch, while unstable feature development proceeds in 9.15.

-
- -
+
+

Download

-

+

The latest versions of BIND 9 software can always be found at http://www.isc.org/downloads/. There you will find additional information about each release, source code, and pre-compiled versions for Microsoft Windows operating systems.

-
- -
+
+

Security Fixes

-
  • -

    +

      +

    • When recursion is enabled but the allow-recursion and allow-query-cache ACLs are not specified, they should be limited to local networks, but they were inadvertently set to match the default allow-query, thus allowing remote queries. This flaw is disclosed in CVE-2018-5738. [GL #309] -

      -
    -
- -
+

+

  • + named could crash during recursive processing + of DNAME records when deny-answer-aliases was + in use. This flaw is disclosed in CVE-2018-5740. [GL #387] +

    • +
    +
    +

    New Features

    -
      -
    • -

      +

        +

      • A new secondary zone option, mirror, enables named to serve a transferred copy of a zone's contents without acting as an authority for the @@ -133,18 +132,14 @@ but do set the AD bit ("authenticated data"). This feature is meant to facilitate deployment of a local copy of the root zone, as described in RFC 7706. [GL #33] -

        -
        • -
      • -

        +

        • +

      • BIND now can be compiled against the libidn2 library to add IDNA2008 support. Previously, BIND supported IDNA2003 using the (now obsolete and unsupported) idnkit-1 library. -

        -
        • -
      • -

        +

        • +

      • named now supports the "root key sentinel" mechanism. This enables validating resolvers to indicate which trust anchors are configured for the root, so that @@ -152,26 +147,20 @@ To disable this feature, add root-key-sentinel no; to named.conf. [GL #37] -

        -
        • -
      • -

        +

        • +

      • The dnskey-sig-validity option allows the sig-validity-interval to be overriden for signatures covering DNSKEY RRsets. [GL #145] -

        -
        • -
      • -

        +

        • +

      • Support for QNAME minimization was added and enabled by default in relaxed mode, in which BIND will fall back to normal resolution if the remote server returns something unexpected during the query minimization process. This default setting might change to strict in the future. -

        -
        • -
      • -

        +

        • +

      • When built on Linux, BIND now requires the libcap library to set process privileges. The adds a new compile-time dependency, which can be met on most Linux platforms by installing the @@ -179,17 +168,67 @@ package. BIND can also be built without capability support by using configure --disable-linux-caps, at the cost of some loss of security. -

        -
        • +

        +

      • + The validate-except option specifies a list of + domains beneath which DNSSEC validation should not be performed, + regardless of whether a trust anchor has been configured above + them. [GL #237] +

      -
    - -
    +
    +

    Removed Features

    -
      +
      • -

        +

        + Workarounds for servers that misbehave when queried with EDNS + have been removed, because these broken servers and the + workarounds for their noncompliance cause unnecessary delays, + increase code complexity, and prevent deployment of new DNS + features. See https://dnsflagday.net + for further details. +

        +

        + In particular, resolution will no longer fall back to + plain DNS when there was no response from an authoritative + server. This will cause some domains to become non-resolvable + without manual intervention. In these cases, resolution can + be restored by adding server clauses for the + offending servers, specifying edns no or + send-cookie no, depending on the specific + noncompliance. +

        +

        + To determine which server clause to use, run + the following commands to send queries to the authoritative + servers for the broken domain: +

        +


        +   dig soa <zone> @<server> +dnssec
        +   dig soa <zone> @<server> +dnssec +nocookie
        +   dig soa <zone> @<server> +noedns
        +

        +

        + If the first command fails but the second succeeds, the + server most likely needs send-cookie no. + If the first two fail but the third succeeds, then the server + needs EDNS to be fully disabled with edns no. +

        +

        + Please contact the administrators of noncompliant domains + and encourage them to upgrade their broken DNS servers. [GL #150] +

        +
        • +

      • + Previously, it was possible to build BIND without thread support + for old architectures and systems without threads support. + BIND now requires threading support (either POSIX or Windows) from + the operating system, and it cannot be built without threads. +

        • +
      • +

        named can no longer use the EDNS CLIENT-SUBNET option for view selection. In its existing form, the authoritative ECS feature was not fully RFC-compliant, and could not realistically @@ -197,7 +236,7 @@ only practical use was for testing and experimentation. In the interest of code simplification, this feature has now been removed.

        -

        +

        The ECS option is still supported in dig and mdig via the +subnet argument, and can be parsed and logged when received by named, but @@ -209,46 +248,34 @@ also obsolete, and will cause the configuration to fail to load if they are used. [GL #32]

        -
        • -
      • -

        +

        • +

      • dnssec-keygen can no longer generate HMAC keys for TSIG authentication. Use tsig-keygen to generate these keys. [RT #46404] -

        -
        • -
      • -

        +

        • +

      • Support for OpenSSL 0.9.x has been removed. OpenSSL version 1.0.0 or greater, or LibreSSL is now required. -

        -
        • -
      • -

        +

        • +

      • The configure --enable-seccomp option, which formerly turned on system-call filtering on Linux, has been removed. [GL #93] -

        -
        • -
      • -

        +

        • +

      • IPv4 addresses in forms other than dotted-quad are no longer accepted in master files. [GL #13] [GL #56] -

        -
        • -
      • -

        +

        • +

      • IDNA2003 support via (bundled) idnkit-1.0 has been removed. -

        -
        • -
      • -

        +

        • +

      • The "rbtdb64" database implementation (a parallel implementation of "rbt") has been removed. [GL #217] -

        -
        • +

      • -

        +

        The -r randomdev option to explicitly select random device has been removed from the ddns-confgen, @@ -257,28 +284,26 @@ dnssec-confgen, and dnssec-signzone commands.

        -

        +

        The -p option to use pseudo-random data has been removed from the dnssec-signzone command.

        -
        • -
      • -

        +

        • +

      • Support for ECC-GOST (GOST R 34.11-94) algorithm has been removed from BIND as the algorithm has been superseded by GOST R 34.11-2012 in RFC6986 and it must not be used in new deployments. BIND will neither create new DNSSEC keys, signatures and digest, nor it will validate them. -

        -
        • +

      • -

        +

        Add the ability to not return a DNS COOKIE option when one is present in the request. To prevent a cookie being returned add 'answer-cookie no;' to named.conf. [GL #173]

        -

        +

        answer-cookie is only intended as a temporary measure, for use when named shares an IP address with other servers that do not yet support DNS COOKIE. A mismatch @@ -288,16 +313,26 @@ abundance of caution. DNS COOKIE is an important security mechanism, and should not be disabled unless absolutely necessary.

        -
        • +

        + Remove support for silently ignoring 'no-change' deltas from + BIND 8 when processing an IXFR stream. 'no-change' deltas + will now trigger a fallback to AXFR as the recovery mechanism. +

        +

        + BIND 9 will no longer build on platforms that doesn't have + proper IPv6 support. BIND 9 now also requires non-broken + POSIX-compatible pthread support. Such platforms are + usually long after their end-of-life date and they are + neither developed nor supported by their respective vendors. +

        +
      -
    - -
    +
    +

    Feature Changes

    -
      -
    • -

      +

        +

      • BIND will now always use the best CSPRNG (cryptographically-secure pseudo-random number generator) available on the platform where it is compiled. It will use arc4random() @@ -306,10 +341,8 @@ CryptGenRandom on Windows, and the selected cryptography provider library (OpenSSL or PKCS#11) as the last resort. [GL #221] -

        -
        • -
      • -

        +

        • +

      • The default setting for dnssec-validation is now auto, which activates DNSSEC validation using the IANA root key. (The default can be changed @@ -317,51 +350,37 @@ validation only when keys are explicitly configured in named.conf, by building BIND with configure --disable-auto-validation.) [GL #30] -

        -
        • -
      • -

        +

        • +

      • BIND can no longer be built without DNSSEC support. A cryptography provder (i.e., OpenSSL or a hardware service module with PKCS#11 support) must be available. [GL #244] -

        -
        • -
      • -

        +

        • +

      • Zone types primary and secondary are now available as synonyms for master and slave, respectively, in named.conf. -

        -
        • -
      • -

        +

        • +

      • named will now log a warning if the old root DNSSEC key is explicitly configured and has not been updated. [RT #43670] -

        -
        • -
      • -

        +

        • +

      • dig +nssearch will now list name servers that have timed out, in addition to those that respond. [GL #64] -

        -
        • -
      • -

        +

        • +

      • dig +noidnin can be used to disable IDN processing on the input domain name, when BIND is compiled with IDN support. -

        -
        • -
      • -

        +

        • +

      • Up to 64 response-policy zones are now supported by default; previously the limit was 32. [GL #123] -

        -
        • -
      • -

        +

        • +

      • Several configuration options for time periods can now use TTL value suffixes (for example, 2h or 1d) in addition to an integer number of @@ -373,40 +392,33 @@ max-policy-ttl, and min-update-interval. [GL #203] -

        -
        • -
      • -

        +

        • +

      • NSID logging (enabled by the request-nsid option) now has its own nsid category, instead of using the resolver category. -

        -
        • +

      -
    - -
    +
    +

    Bug Fixes

    -
    • -

      +

      • named now rejects excessively large incremental (IXFR) zone transfers in order to prevent possible corruption of journal files which could cause named to abort when loading zones. [GL #339] -

        -
      -
    - -
    +

    +
    +

    License

    -

    +

    BIND is open source software licenced under the terms of the Mozilla Public License, version 2.0 (see the LICENSE file for the full text).

    -

    +

    The license requires that if you make changes to BIND and distribute them outside your organization, those changes must be published under the same license. It does not require that you publish or disclose @@ -415,22 +427,21 @@ modifications, without redistributing it, nor anyone redistributing BIND without changes.

    -

    +

    Those wishing to discuss license compliance may contact ISC at https://www.isc.org/mission/contact/.

    -
    - -
    +
    +

    End of Life

    -

    +

    BIND 9.13 is an unstable development branch. When its development is complete, it will be renamed to BIND 9.14, which will be a stable branch.

    -

    +

    The end of life date for BIND 9.14 has not yet been determined. For those needing long term support, the current Extended Support Version (ESV) is BIND 9.11, which will be supported until at @@ -438,20 +449,19 @@ https://www.isc.org/downloads/software-support-policy/ for details of ISC's software support policy.

    -
    - -
    +
    +

    Thank You

    -

    +

    Thank you to everyone who assisted us in making this release possible. If you would like to contribute to ISC to assist us in continuing to make quality open source software, please visit our donations page at http://www.isc.org/donate/.

    -
    -
    +
    +
    @@ -470,6 +480,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html index 30e233636c29cbc2e62f37ae220023acefc94629..fc941f4aa808d72ef2a8092c0ef2f83faac6d963 100644 --- a/doc/arm/Bv9ARM.ch09.html +++ b/doc/arm/Bv9ARM.ch09.html @@ -10,7 +10,7 @@ Appendix B. A Brief History of the DNS and BIND - + @@ -35,7 +35,7 @@

    A Brief History of the DNS and BIND

    -

    +

    Although the "official" beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the core of the new system was described in 1983 in RFCs 882 and @@ -50,8 +50,7 @@ became the standards upon which all DNS implementations are built.

    - -

    +

    The first working domain name server, called "Jeeves", was written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 @@ -69,7 +68,7 @@ Administration (DARPA).

    -

    +

    Versions of BIND through 4.8.3 were maintained by the Computer Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark @@ -84,7 +83,7 @@ Mike Muuss, Jim Bloom and Mike Schwartz. BIND maintenance was subsequently handled by Mike Karels and Øivind Kure.

    -

    +

    BIND versions 4.9 and 4.9.1 were released by Digital Equipment Corporation (now Compaq Computer Corporation). Paul Vixie, then @@ -96,41 +95,41 @@ Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe Wolfhugel, and others.

    -

    +

    In 1994, BIND version 4.9.2 was sponsored by Vixie Enterprises. Paul Vixie became BIND's principal architect/programmer.

    -

    +

    BIND versions from 4.9.3 onward have been developed and maintained by the Internet Systems Consortium and its predecessor, the Internet Software Consortium, with support being provided by ISC's sponsors.

    -

    +

    As co-architects/programmers, Bob Halley and Paul Vixie released the first production-ready version of BIND version 8 in May 1997.

    -

    +

    BIND version 9 was released in September 2000 and is a major rewrite of nearly all aspects of the underlying BIND architecture.

    -

    +

    BIND versions 4 and 8 are officially deprecated. No additional development is done on BIND version 4 or BIND version 8.

    -

    +

    BIND development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.

    - +
    @@ -148,6 +147,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/Bv9ARM.ch10.html b/doc/arm/Bv9ARM.ch10.html index cc3761924e6cda6cd13f5ac9ddf710d092e4ff6d..429ec005fb38d1080bc3fed4f4547ca9e9f3dec8 100644 --- a/doc/arm/Bv9ARM.ch10.html +++ b/doc/arm/Bv9ARM.ch10.html @@ -10,7 +10,7 @@ Appendix C. General DNS Reference Information - + @@ -45,12 +45,10 @@ - -
    +

    IPv6 addresses (AAAA)

    - -

    +

    IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces which were introduced in the DNS to facilitate scalable Internet routing. There are three types of addresses: Unicast, @@ -61,13 +59,13 @@ Unicast address scheme. For more information, see RFC 3587, "Global Unicast Address Format."

    -

    +

    IPv6 unicast addresses consist of a global routing prefix, a subnet identifier, and an interface identifier.

    -

    +

    The global routing prefix is provided by the upstream provider or ISP, and (roughly) corresponds to the IPv4 network section @@ -81,14 +79,14 @@ interface on a given network; in IPv6, addresses belong to interfaces rather than to machines.

    -

    +

    The subnetting capability of IPv6 is much more flexible than that of IPv4: subnetting can be carried out on bit boundaries, in much the same way as Classless InterDomain Routing (CIDR), and the DNS PTR representation ("nibble" format) makes setting up reverse zones easier.

    -

    +

    The Interface Identifier must be unique on the local link, and is usually generated automatically by the IPv6 implementation, although it is usually possible to @@ -96,7 +94,7 @@ address might look like: 2001:db8:201:9:a00:20ff:fe81:2b32

    -

    +

    IPv6 address specifications often contain long strings of zeros, so the architects have included a shorthand for specifying @@ -104,16 +102,14 @@ string of zeros that can fit, and can be used only once in an address.

    -
    -
    +
    +

    Bibliography (and Suggested Reading)

    - -
    +

    Request for Comments (RFCs)

    - -

    +

    Specification documents for the Internet protocol suite, including the DNS, are published as part of the Request for Comments (RFCs) @@ -121,752 +117,336 @@ by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG). RFCs can be obtained online via FTP at:

    -

    +

    ftp://www.isi.edu/in-notes/RFCxxxx.txt

    -

    +

    (where xxxx is the number of the RFC). RFCs are also available via the Web at:

    -

    +

    http://www.ietf.org/rfc/.

    -
    +

    Bibliography

    -
    - - -
    -

    [RFC974] - - C. Partridge. - Mail Routing and the Domain System. - January 1986. -

    -
    -
    -

    [RFC1034] - - P.V. Mockapetris. - Domain Names — Concepts and Facilities. - November 1987. -

    -
    -
    -

    [RFC1035] - - P. V. Mockapetris. Domain Names — Implementation and - Specification. - November 1987. -

    -
    -
    -
    - - -
    -

    [RFC2181] - - R., R. Bush Elz. - Clarifications to the DNS - Specification. - July 1997. -

    -
    -
    -

    [RFC2308] - - M. Andrews. - Negative Caching of DNS - Queries. - March 1998. -

    -
    -
    -

    [RFC1995] - - M. Ohta. - Incremental Zone Transfer in DNS. - August 1996. -

    -
    -
    -

    [RFC1996] - - P. Vixie. - A Mechanism for Prompt Notification of Zone Changes. - August 1996. -

    -
    -
    -

    [RFC2136] - - P. Vixie, S. Thomson, Y. Rekhter, and J. Bound. - Dynamic Updates in the Domain Name System. - April 1997. -

    -
    -
    -

    [RFC2671] - - P. Vixie. - Extension Mechanisms for DNS (EDNS0). - August 1997. -

    -
    -
    -

    [RFC2672] - - M. Crawford. - Non-Terminal DNS Name Redirection. - August 1999. -

    -
    -
    -

    [RFC2845] - - P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington. - Secret Key Transaction Authentication for DNS (TSIG). - May 2000. -

    -
    -
    -

    [RFC2930] - - D. Eastlake, 3rd. - Secret Key Establishment for DNS (TKEY RR). - September 2000. -

    -
    -
    -

    [RFC2931] - - D. Eastlake, 3rd. - DNS Request and Transaction Signatures (SIG(0)s). - September 2000. -

    -
    -
    -

    [RFC3007] - - B. Wellington. - Secure Domain Name System (DNS) Dynamic Update. - November 2000. -

    -
    -
    -

    [RFC3645] - - S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. - Generic Security Service Algorithm for Secret +

    +
    +

    [RFC974] C. Partridge. Mail Routing and the Domain System. January 1986.

    +
    +
    +

    [RFC1034] P.V. Mockapetris. Domain Names — Concepts and Facilities. November 1987.

    +
    +
    +

    [RFC1035] P. V. Mockapetris. Domain Names — Implementation and + Specification. November 1987.

    +
    +
    +
    +
    +

    [RFC2181] R., R. Bush Elz. Clarifications to the DNS + Specification. July 1997.

    +
    +
    +

    [RFC2308] M. Andrews. Negative Caching of DNS + Queries. March 1998.

    +
    +
    +

    [RFC1995] M. Ohta. Incremental Zone Transfer in DNS. August 1996.

    +
    +
    +

    [RFC1996] P. Vixie. A Mechanism for Prompt Notification of Zone Changes. August 1996.

    +
    +
    +

    [RFC2136] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound. Dynamic Updates in the Domain Name System. April 1997.

    +
    +
    +

    [RFC2671] P. Vixie. Extension Mechanisms for DNS (EDNS0). August 1997.

    +
    +
    +

    [RFC2672] M. Crawford. Non-Terminal DNS Name Redirection. August 1999.

    +
    +
    +

    [RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington. Secret Key Transaction Authentication for DNS (TSIG). May 2000.

    +
    +
    +

    [RFC2930] D. Eastlake, 3rd. Secret Key Establishment for DNS (TKEY RR). September 2000.

    +
    +
    +

    [RFC2931] D. Eastlake, 3rd. DNS Request and Transaction Signatures (SIG(0)s). September 2000.

    +
    +
    +

    [RFC3007] B. Wellington. Secure Domain Name System (DNS) Dynamic Update. November 2000.

    +
    +
    +

    [RFC3645] S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. Generic Security Service Algorithm for Secret Key Transaction Authentication for DNS - (GSS-TSIG). - October 2003. -

    + (GSS-TSIG)    . October 2003.

    -
    -
    - -
    -

    [RFC3225] - - D. Conrad. - Indicating Resolver Support of DNSSEC. - December 2001. -

    -
    -
    -

    [RFC3833] - - D. Atkins and R. Austein. - Threat Analysis of the Domain Name System (DNS). - August 2004. -

    -
    -
    -

    [RFC4033] - - R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. - DNS Security Introduction and Requirements. - March 2005. -

    -
    -
    -

    [RFC4034] - - R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. - Resource Records for the DNS Security Extensions. - March 2005. -

    -
    -
    -

    [RFC4035] - - R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. - Protocol Modifications for the DNS - Security Extensions. - March 2005. -

    -
    -
    -
    - -
    -

    [RFC1535] - - E. Gavron. - A Security Problem and Proposed Correction With Widely - Deployed DNS Software. - October 1993. -

    -
    -
    -

    [RFC1536] - - A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller. - Common DNS Implementation - Errors and Suggested Fixes. - October 1993. -

    -
    -
    -

    [RFC1982] - - R. Elz and R. Bush. - Serial Number Arithmetic. - August 1996. -

    -
    -
    -

    [RFC4074] - - Y. Morishita and T. Jinmei. - Common Misbehaviour Against DNS - Queries for IPv6 Addresses. - May 2005. -

    -
    -
    -
    - -
    -

    [RFC1183] - - C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris. - New DNS RR Definitions. - October 1990. -

    -
    -
    -

    [RFC1706] - - B. Manning and R. Colella. - DNS NSAP Resource Records. - October 1994. -

    -
    -
    -

    [RFC2168] - - R. Daniel and M. Mealling. - Resolution of Uniform Resource Identifiers using - the Domain Name System. - June 1997. -

    -
    -
    -

    [RFC1876] - - C. Davis, P. Vixie, T., and I. Dickinson. - A Means for Expressing Location Information in the +

    +
    +
    +

    [RFC3225] D. Conrad. Indicating Resolver Support of DNSSEC. December 2001.

    +
    +
    +

    [RFC3833] D. Atkins and R. Austein. Threat Analysis of the Domain Name System (DNS). August 2004.

    +
    +
    +

    [RFC4033] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. March 2005.

    +
    +
    +

    [RFC4034] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Resource Records for the DNS Security Extensions. March 2005.

    +
    +
    +

    [RFC4035] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Protocol Modifications for the DNS + Security Extensions. March 2005.

    +
    +
    +
    +
    +

    [RFC1535] E. Gavron. A Security Problem and Proposed Correction With Widely + Deployed DNS Software. October 1993.

    +
    +
    +

    [RFC1536] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller. Common DNS Implementation + Errors and Suggested Fixes. October 1993.

    +
    +
    +

    [RFC1982] R. Elz and R. Bush. Serial Number Arithmetic. August 1996.

    +
    +
    +

    [RFC4074] Y. Morishita and T. Jinmei. Common Misbehaviour Against DNS + Queries for IPv6 Addresses. May 2005.

    +
    +
    +
    +
    +

    [RFC1183] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris. New DNS RR Definitions. October 1990.

    +
    +
    +

    [RFC1706] B. Manning and R. Colella. DNS NSAP Resource Records. October 1994.

    +
    +
    +

    [RFC2168] R. Daniel and M. Mealling. Resolution of Uniform Resource Identifiers using + the Domain Name System. June 1997.

    +
    +
    +

    [RFC1876] C. Davis, P. Vixie, T., and I. Dickinson. A Means for Expressing Location Information in the Domain - Name System. - January 1996. -

    -
    -
    -

    [RFC2052] - - A. Gulbrandsen and P. Vixie. - A DNS RR for Specifying the + Name System. January 1996.

    +
    +
    +

    [RFC2052] A. Gulbrandsen and P. Vixie. A DNS RR for Specifying the Location of - Services. - October 1996. -

    -
    -
    -

    [RFC2163] - - A. Allocchio. - Using the Internet DNS to + Services. October 1996.

    +
    +
    +

    [RFC2163] A. Allocchio. Using the Internet DNS to Distribute MIXER - Conformant Global Address Mapping. - January 1998. -

    -
    -
    -

    [RFC2230] - - R. Atkinson. - Key Exchange Delegation Record for the DNS. - October 1997. -

    -
    -
    -

    [RFC2536] - - D. Eastlake, 3rd. - DSA KEYs and SIGs in the Domain Name System (DNS). - March 1999. -

    -
    -
    -

    [RFC2537] - - D. Eastlake, 3rd. - RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). - March 1999. -

    -
    -
    -

    [RFC2538] - - D. Eastlake, 3rd and O. Gudmundsson. - Storing Certificates in the Domain Name System (DNS). - March 1999. -

    -
    -
    -

    [RFC2539] - - D. Eastlake, 3rd. - Storage of Diffie-Hellman Keys in the Domain Name System (DNS). - March 1999. -

    -
    -
    -

    [RFC2540] - - D. Eastlake, 3rd. - Detached Domain Name System (DNS) Information. - March 1999. -

    -
    -
    -

    [RFC2782] - - A. Gulbrandsen. - P. Vixie. - L. Esibov. - A DNS RR for specifying the location of services (DNS SRV). - February 2000. -

    -
    -
    -

    [RFC2915] - - M. Mealling. - R. Daniel. - The Naming Authority Pointer (NAPTR) DNS Resource Record. - September 2000. -

    -
    -
    -

    [RFC3110] - - D. Eastlake, 3rd. - RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). - May 2001. -

    -
    -
    -

    [RFC3123] - - P. Koch. - A DNS RR Type for Lists of Address Prefixes (APL RR). - June 2001. -

    -
    -
    -

    [RFC3596] - - S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. - DNS Extensions to support IP - version 6. - October 2003. -

    -
    -
    -

    [RFC3597] - - A. Gustafsson. - Handling of Unknown DNS Resource Record (RR) Types. - September 2003. -

    -
    -
    -
    - -
    -

    [RFC1101] - - P. V. Mockapetris. - DNS Encoding of Network Names - and Other Types. - April 1989. -

    -
    -
    -

    [RFC1123] - - Braden. - Requirements for Internet Hosts - Application and - Support. - October 1989. -

    -
    -
    -

    [RFC1591] - - J. Postel. - Domain Name System Structure and Delegation. - March 1994. -

    -
    -
    -

    [RFC2317] - - H. Eidnes, G. de Groot, and P. Vixie. - Classless IN-ADDR.ARPA Delegation. - March 1998. -

    -
    -
    -

    [RFC2826] - - Internet Architecture Board. - IAB Technical Comment on the Unique DNS Root. - May 2000. -

    -
    -
    -

    [RFC2929] - - D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. - Domain Name System (DNS) IANA Considerations. - September 2000. -

    -
    -
    -
    - -
    -

    [RFC1033] - - M. Lottor. - Domain administrators operations guide. - November 1987. -

    -
    -
    -

    [RFC1537] - - P. Beertema. - Common DNS Data File - Configuration Errors. - October 1993. -

    -
    -
    -

    [RFC1912] - - D. Barr. - Common DNS Operational and - Configuration Errors. - February 1996. -

    -
    -
    -

    [RFC2010] - - B. Manning and P. Vixie. - Operational Criteria for Root Name Servers. - October 1996. -

    -
    -
    -

    [RFC2219] - - M. Hamilton and R. Wright. - Use of DNS Aliases for - Network Services. - October 1997. -

    -
    -
    -
    - -
    -

    [RFC2825] - - IAB and R. Daigle. - A Tangled Web: Issues of I18N, Domain Names, - and the Other Internet protocols. - May 2000. -

    -
    -
    -

    [RFC3490] - - P. Faltstrom, P. Hoffman, and A. Costello. - Internationalizing Domain Names in Applications (IDNA). - March 2003. -

    -
    -
    -

    [RFC3491] - - P. Hoffman and M. Blanchet. - Nameprep: A Stringprep Profile for Internationalized Domain Names. - March 2003. -

    -
    -
    -

    [RFC3492] - - A. Costello. - Punycode: A Bootstring encoding of Unicode + Conformant Global Address Mapping. January 1998.

    +
    +
    +

    [RFC2230] R. Atkinson. Key Exchange Delegation Record for the DNS. October 1997.

    +
    +
    +

    [RFC2536] D. Eastlake, 3rd. DSA KEYs and SIGs in the Domain Name System (DNS). March 1999.

    +
    +
    +

    [RFC2537] D. Eastlake, 3rd. RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). March 1999.

    +
    +
    +

    [RFC2538] D. Eastlake, 3rd and O. Gudmundsson. Storing Certificates in the Domain Name System (DNS). March 1999.

    +
    +
    +

    [RFC2539] D. Eastlake, 3rd. Storage of Diffie-Hellman Keys in the Domain Name System (DNS). March 1999.

    +
    +
    +

    [RFC2540] D. Eastlake, 3rd. Detached Domain Name System (DNS) Information. March 1999.

    +
    +
    +

    [RFC2782] A. Gulbrandsen. P. Vixie. L. Esibov. A DNS RR for specifying the location of services (DNS SRV). February 2000.

    +
    +
    +

    [RFC2915] M. Mealling. R. Daniel. The Naming Authority Pointer (NAPTR) DNS Resource Record. September 2000.

    +
    +
    +

    [RFC3110] D. Eastlake, 3rd. RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). May 2001.

    +
    +
    +

    [RFC3123] P. Koch. A DNS RR Type for Lists of Address Prefixes (APL RR). June 2001.

    +
    +
    +

    [RFC3596] S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. DNS Extensions to support IP + version 6. October 2003.

    +
    +
    +

    [RFC3597] A. Gustafsson. Handling of Unknown DNS Resource Record (RR) Types. September 2003.

    +
    +
    +
    +
    +

    [RFC1101] P. V. Mockapetris. DNS Encoding of Network Names + and Other Types. April 1989.

    +
    +
    +

    [RFC1123] Braden. Requirements for Internet Hosts - Application and + Support. October 1989.

    +
    +
    +

    [RFC1591] J. Postel. Domain Name System Structure and Delegation. March 1994.

    +
    +
    +

    [RFC2317] H. Eidnes, G. de Groot, and P. Vixie. Classless IN-ADDR.ARPA Delegation. March 1998.

    +
    +
    +

    [RFC2826] Internet Architecture Board. IAB Technical Comment on the Unique DNS Root. May 2000.

    +
    +
    +

    [RFC2929] D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. Domain Name System (DNS) IANA Considerations. September 2000.

    +
    +
    +
    +
    +

    [RFC1033] M. Lottor. Domain administrators operations guide. November 1987.

    +
    +
    +

    [RFC1537] P. Beertema. Common DNS Data File + Configuration Errors. October 1993.

    +
    +
    +

    [RFC1912] D. Barr. Common DNS Operational and + Configuration Errors. February 1996.

    +
    +
    +

    [RFC2010] B. Manning and P. Vixie. Operational Criteria for Root Name Servers. October 1996.

    +
    +
    +

    [RFC2219] M. Hamilton and R. Wright. Use of DNS Aliases for + Network Services. October 1997.

    +
    +
    +
    +
    +

    [RFC2825] IAB and R. Daigle. A Tangled Web: Issues of I18N, Domain Names, + and the Other Internet protocols. May 2000.

    +
    +
    +

    [RFC3490] P. Faltstrom, P. Hoffman, and A. Costello. Internationalizing Domain Names in Applications (IDNA). March 2003.

    +
    +
    +

    [RFC3491] P. Hoffman and M. Blanchet. Nameprep: A Stringprep Profile for Internationalized Domain Names. March 2003.

    +
    +
    +

    [RFC3492] A. Costello. Punycode: A Bootstring encoding of Unicode for Internationalized Domain Names in - Applications (IDNA). - March 2003. -

    + Applications (IDNA)    . March 2003.

    -
    -
    - -
    +
    +
    +

    Note

    -

    +

    Note: the following list of RFCs, although DNS-related, are not concerned with implementing software.

    -
    -
    -

    [RFC1464] - - R. Rosenbaum. - Using the Domain Name System To Store Arbitrary String - Attributes. - May 1993. -

    -
    -
    -

    [RFC1713] - - A. Romao. - Tools for DNS Debugging. - November 1994. -

    -
    -
    -

    [RFC1794] - - T. Brisco. - DNS Support for Load - Balancing. - April 1995. -

    -
    -
    -

    [RFC2240] - - O. Vaughan. - A Legal Basis for Domain Name Allocation. - November 1997. -

    -
    -
    -

    [RFC2345] - - J. Klensin, T. Wolf, and G. Oglesby. - Domain Names and Company Name Retrieval. - May 1998. -

    -
    -
    -

    [RFC2352] - - O. Vaughan. - A Convention For Using Legal Names as Domain Names. - May 1998. -

    -
    -
    -

    [RFC3071] - - J. Klensin. - Reflections on the DNS, RFC 1591, and Categories of Domains. - February 2001. -

    -
    -
    -

    [RFC3258] - - T. Hardie. - Distributing Authoritative Name Servers via - Shared Unicast Addresses. - April 2002. -

    -
    -
    -

    [RFC3901] - - A. Durand and J. Ihren. - DNS IPv6 Transport Operational Guidelines. - September 2004. -

    -
    -
    -
    - -
    -

    [RFC1712] - - C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni. - DNS Encoding of Geographical - Location. - November 1994. -

    -
    -
    -

    [RFC2673] - - M. Crawford. - Binary Labels in the Domain Name System. - August 1999. -

    -
    -
    -

    [RFC2874] - - M. Crawford and C. Huitema. - DNS Extensions to Support IPv6 Address Aggregation - and Renumbering. - July 2000. -

    -
    -
    -
    - -
    +
    +
    +

    [RFC1464] R. Rosenbaum. Using the Domain Name System To Store Arbitrary String + Attributes. May 1993.

    +
    +
    +

    [RFC1713] A. Romao. Tools for DNS Debugging. November 1994.

    +
    +
    +

    [RFC1794] T. Brisco. DNS Support for Load + Balancing. April 1995.

    +
    +
    +

    [RFC2240] O. Vaughan. A Legal Basis for Domain Name Allocation. November 1997.

    +
    +
    +

    [RFC2345] J. Klensin, T. Wolf, and G. Oglesby. Domain Names and Company Name Retrieval. May 1998.

    +
    +
    +

    [RFC2352] O. Vaughan. A Convention For Using Legal Names as Domain Names. May 1998.

    +
    +
    +

    [RFC3071] J. Klensin. Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001.

    +
    +
    +

    [RFC3258] T. Hardie. Distributing Authoritative Name Servers via + Shared Unicast Addresses. April 2002.

    +
    +
    +

    [RFC3901] A. Durand and J. Ihren. DNS IPv6 Transport Operational Guidelines. September 2004.

    +
    +
    +
    +
    +

    [RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni. DNS Encoding of Geographical + Location. November 1994.

    +
    +
    +

    [RFC2673] M. Crawford. Binary Labels in the Domain Name System. August 1999.

    +
    +
    +

    [RFC2874] M. Crawford and C. Huitema. DNS Extensions to Support IPv6 Address Aggregation + and Renumbering. July 2000.

    +
    +
    +
    +

    Note

    -

    +

    Most of these have been consolidated into RFC4033, RFC4034 and RFC4035 which collectively describe DNSSECbis.

    -
    -
    -

    [RFC2065] - - D. Eastlake, 3rd and C. Kaufman. - Domain Name System Security Extensions. - January 1997. -

    -
    -
    -

    [RFC2137] - - D. Eastlake, 3rd. - Secure Domain Name System Dynamic Update. - April 1997. -

    -
    -
    -

    [RFC2535] - - D. Eastlake, 3rd. - Domain Name System Security Extensions. - March 1999. -

    -
    -
    -

    [RFC3008] - - B. Wellington. - Domain Name System Security (DNSSEC) - Signing Authority. - November 2000. -

    -
    -
    -

    [RFC3090] - - E. Lewis. - DNS Security Extension Clarification on Zone Status. - March 2001. -

    -
    -
    -

    [RFC3445] - - D. Massey and S. Rose. - Limiting the Scope of the KEY Resource Record (RR). - December 2002. -

    -
    -
    -

    [RFC3655] - - B. Wellington and O. Gudmundsson. - Redefinition of DNS Authenticated Data (AD) bit. - November 2003. -

    -
    -
    -

    [RFC3658] - - O. Gudmundsson. - Delegation Signer (DS) Resource Record (RR). - December 2003. -

    -
    -
    -

    [RFC3755] - - S. Weiler. - Legacy Resolver Compatibility for Delegation Signer (DS). - May 2004. -

    -
    -
    -

    [RFC3757] - - O. Kolkman, J. Schlyter, and E. Lewis. - Domain Name System KEY (DNSKEY) Resource Record - (RR) Secure Entry Point (SEP) Flag. - April 2004. -

    -
    -
    -

    [RFC3845] - - J. Schlyter. - DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. - August 2004. -

    -
    -
    -
    -
    -
    +
    +
    +

    [RFC2065] D. Eastlake, 3rd and C. Kaufman. Domain Name System Security Extensions. January 1997.

    +
    +
    +

    [RFC2137] D. Eastlake, 3rd. Secure Domain Name System Dynamic Update. April 1997.

    +
    +
    +

    [RFC2535] D. Eastlake, 3rd. Domain Name System Security Extensions. March 1999.

    +
    +
    +

    [RFC3008] B. Wellington. Domain Name System Security (DNSSEC) + Signing Authority. November 2000.

    +
    +
    +

    [RFC3090] E. Lewis. DNS Security Extension Clarification on Zone Status. March 2001.

    +
    +
    +

    [RFC3445] D. Massey and S. Rose. Limiting the Scope of the KEY Resource Record (RR). December 2002.

    +
    +
    +

    [RFC3655] B. Wellington and O. Gudmundsson. Redefinition of DNS Authenticated Data (AD) bit. November 2003.

    +
    +
    +

    [RFC3658] O. Gudmundsson. Delegation Signer (DS) Resource Record (RR). December 2003.

    +
    +
    +

    [RFC3755] S. Weiler. Legacy Resolver Compatibility for Delegation Signer (DS). May 2004.

    +
    +
    +

    [RFC3757] O. Kolkman, J. Schlyter, and E. Lewis. Domain Name System KEY (DNSKEY) Resource Record + (RR) Secure Entry Point (SEP) Flag. April 2004.

    +
    +
    +

    [RFC3845] J. Schlyter. DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004.

    +
    +
    +
    +
    +

    Internet Drafts

    - -

    +

    Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs in the preliminary stages of development. Implementors are @@ -876,27 +456,22 @@ they are "works in progress." IDs have a lifespan of six months after which they are deleted unless updated by their authors.

    -
    -
    +
    +

    Other Documents About BIND

    - -

    -
    +

    +

    Bibliography

    -
    -

    - Paul Albitz and Cricket Liu. - DNS and BIND. - Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. -

    -
    -
    -
    -
    -
    +
    +

    Paul Albitz and Cricket Liu. DNS and BIND. Copyright © 1998 Sebastopol, CA: O'Reilly and Associates.

    +
    +
    +
    +
    +
    @@ -914,6 +489,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/Bv9ARM.ch11.html b/doc/arm/Bv9ARM.ch11.html index 41f0c4c4b5fee81e09543524e9d3ad4eb9239ab4..e2704db4863012cec2a34192001c3b7f1091705b 100644 --- a/doc/arm/Bv9ARM.ch11.html +++ b/doc/arm/Bv9ARM.ch11.html @@ -10,7 +10,7 @@ Appendix D. BIND 9 DNS Library Support - + @@ -46,11 +46,10 @@ -
    +

    BIND 9 DNS Library Support

    - -

    +

    This version of BIND 9 "exports" its internal libraries so that they can be used by third-party applications more easily (we call them "export" libraries in this document). Certain library @@ -59,32 +58,27 @@ the calling program initializes the libraries by calling isc_lib_register().

    -

    +

    In addition to DNS-related APIs that are used within BIND 9, the libraries provide the following features:

    -
      -
    • -

      +

        +

      • The "DNS client" module. This is a higher level API that provides an interface to name resolution, single DNS transaction with a particular server, and dynamic update. Regarding name resolution, it supports advanced features such as DNSSEC validation and caching. This module supports both synchronous and asynchronous mode. -

        -
        • -
      • -

        +

        • +

      • The "IRS" (Information Retrieval System) library. It provides an interface to parse the traditional resolv.conf file and more advanced, DNS-specific configuration file for the rest of this package (see the description for the dns.conf file below). -

        -
        • -
      • -

        +

        • +

      • As part of the IRS library, the standard address-name mapping functions, getaddrinfo() and getnameinfo(), are provided. They use the @@ -93,38 +87,33 @@ getaddrinfo() function resolves both A and AAAA RRs concurrently when the address family is unspecified. -

        -
        • -
      • -

        +

        • +

      • An experimental framework to support other event libraries than BIND 9's internal event task system. -

        -
        • +

      -
      +

      Installation

      - - 
      +
       $ make install
     
      
-    
      
+
      
       Normal installation of BIND will also install library object
       and header files.  Root privilege is normally required.
     
      
-    
      
+
      
       To see how to build your own application after the installation, see
       lib/samples/Makefile-postinstall.in.
     
      
-
      -
      +
      +

      Known Defects/Restrictions

      - -
        +
        • -

          +

          The "fixed" RRset order is not (currently) supported in the export library. If you want to use "fixed" RRset order for, e.g. named while still building the export library @@ -139,30 +128,25 @@ $ make

          -
          • -
        • -

          +

          • +

        • RFC 5011 is not supported in the validating stub resolver of the export library. In fact, it is not clear whether it should: trust anchors would be a system-wide configuration which would be managed by an administrator, while the stub resolver will be used by ordinary applications run by a normal user. -

          -
          • -
        • -

          +

          • +

        • Not all common /etc/resolv.conf options are supported in the IRS library. The only available options in this version are debug and ndots. -

          -
          • +

        -
      -
      +
      +

      The dns.conf File

      - -

      +

      The IRS library supports an "advanced" configuration file related to the DNS library for configuration parameters that would be beyond the capability of the resolv.conf file. @@ -175,42 +159,38 @@ $ make statement in named.conf. (See the section called “trusted-keys Statement Grammar” for details.)

      -
      -
      +
      +

      Sample Applications

      - -

      +

      Some sample application programs using this API are provided for reference. The following is a brief description of these applications.

      -
      +

      sample: a simple stub resolver utility

      - -

      +

      Sends a query of a given name (of a given optional RR type) to a specified recursive server and prints the result as a list of RRs. It can also act as a validating stub resolver if a trust anchor is given via a set of command line options.

      -

      +

      Usage: sample [options] server_address hostname

      -

      +

      Options and Arguments:

      -
      +
      -t RRtype
      -
      -

      +

      specify the RR type of the query. The default is the A RR. -

      -
      +

      [-a algorithm] [-e] -k keyname -K keystring
      -

      +

      specify a command-line DNS key to validate the answer. For example, to specify the following DNSKEY of example.com:

      @@ -228,43 +208,36 @@ $ make as "secure entry point"). When -a is omitted rsasha1 will be used by default.

      -
      +
      -s domain:alt_server_address
      -
      -

      +

      specify a separate recursive server address for the specific "domain". Example: -s example.com:2001:db8::1234 -

      -
      +

      server_address
      -
      -

      +

      an IP(v4/v6) address of the recursive server to which queries are sent. -

      -
      +

      hostname
      -
      -

      +

      the domain name for the query -

      -
      +

      -
      -
      +
      +

      sample-async: a simple stub resolver, working asynchronously

      - -

      +

      Similar to "sample", but accepts a list of (query) domain names as a separate file and resolves the names asynchronously.

      -

      +

      Usage: sample-async [-s server_address] [-t RR_type] input_file

      -

      +

      Options and Arguments:

      -
      +
      -s server_address
      an IPv4 address of the recursive server to which queries are sent. @@ -284,14 +257,13 @@ $ make       mx.example.net
            ns.xxx.example
            

      - +
      -
      -
      +
      +

      sample-request: a simple DNS transaction client

      - -

      +

      Sends a query to a specified server, and prints the response with minimal processing. It doesn't act as a "stub resolver": it stops the processing once it gets any response from the server, whether @@ -299,39 +271,32 @@ $ make further queries to get the ultimate answer. In other words, this utility acts as a very simplified dig.

      -

      +

      Usage: sample-request [-t RRtype] server_address hostname

      -

      +

      Options and Arguments:

      -
      +
      -t RRtype
      -
      -

      +

      specify the RR type of the queries. The default is the A RR. -

      -
      +

      server_address
      -
      -

      +

      an IP(v4/v6) address of the recursive server to which the query is sent. -

      -
      +

      hostname
      -
      -

      +

      the domain name for the query -

      -
      +

      -
      -
      +
      +

      sample-gai: getaddrinfo() and getnameinfo() test code

      - -

      +

      This is a test program to check getaddrinfo() and getnameinfo() behavior. It takes a host name as an argument, calls getaddrinfo() with the given host @@ -343,153 +308,130 @@ $ make will fail with an EAI_INSECUREDATA error when DNSSEC validation fails.

      -

      +

      Usage: sample-gai hostname

      -
      -
      +
      +

      sample-update: a simple dynamic update client program

      - -

      +

      Accepts a single update command as a command-line argument, sends an update request message to the authoritative server, and shows the response from the server. In other words, this is a simplified nsupdate.

      -

      +

      Usage: sample-update [options] (add|delete) "update data"

      -

      +

      Options and Arguments:

      -
      +
      -a auth_server
      -
      -

      +

      An IP address of the authoritative server that has authority for the zone containing the update name. This should normally be the primary authoritative server that accepts dynamic updates. It can also be a secondary server that is configured to forward update requests to the primary server. -

      -
      +

      -k keyfile
      -
      -

      +

      A TSIG key file to secure the update transaction. The keyfile format is the same as that for the nsupdate utility. -

      -
      +

      -p prerequisite
      -
      -

      +

      A prerequisite for the update (only one prerequisite can be specified). The prerequisite format is the same as that is accepted by the nsupdate utility. -

      -
      +

      -r recursive_server
      -
      -

      +

      An IP address of a recursive server that this utility will use. A recursive server may be necessary to identify the authoritative server address to which the update request is sent. -

      -
      +

      -z zonename
      -
      -

      +

      The domain name of the zone that contains -

      -
      +

      (add|delete)
      -
      -

      +

      Specify the type of update operation. Either "add" or "delete" must be specified. -

      -
      +

      "update data"
      -
      -

      +

      Specify the data to be updated. A typical example of the data would look like "name TTL RRtype RDATA". -

      -
      +

      -
      +

      Note

      -

      +

      In practice, either -a or -r must be specified. Others can be optional; the underlying library routine tries to identify the appropriate server and the zone name for the update.

      -
      -

      +

      +

      Examples: assuming the primary authoritative server of the dynamic.example.com zone has an IPv6 address 2001:db8::1234,

      - 
      +
       $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key add "foo.dynamic.example.com 30 IN A 192.168.2.1"
      
-      
      
+
      
 	adds an A RR for foo.dynamic.example.com using the given key.
       
      
-      
      +
       $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com 30 IN A"
      
-      
      
+
      
 	removes all A RRs for foo.dynamic.example.com using the given key.
       
      
-      
      +
       $ sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com"
      
-      
      
+
      
 	removes all RRs for foo.dynamic.example.com using the given key.
       
      
-
      -
      +
      +

      nsprobe: domain/name server checker in terms of RFC 4074

      - -

      +

      Checks a set of domains to see the name servers of the domains behave correctly in terms of RFC 4074. This is included in the set of sample programs to show how the export library can be used in a DNS-related application.

      -

      +

      Usage: nsprobe [-d] [-v [-v...]] [-c cache_address] [input_file]

      -

      +

      Options

      -
      +
      -d
      -
      -

      +

      Run in "debug" mode. With this option nsprobe will dump every RRs it receives. -

      -
      +

      -v
      -
      -

      +

      Increase verbosity of other normal log messages. This can be specified multiple times. -

      -
      +

      -c cache_address
      -
      -

      +

      Specify an IP address of a recursive (caching) name server. nsprobe uses this server to get the NS RRset of each domain and the A and/or AAAA RRsets for the name servers. The default value is 127.0.0.1. -

      -
      +

      input_file
      -
      -

      +

      A file name containing a list of domain (zone) names to be probed. when omitted the standard input will be used. Each line of the input file specifies a single domain name such as @@ -499,23 +441,21 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mm for the given domain name, and sends A and AAAA queries to these servers for some "widely used" names under the zone; specifically, adding "www" and "ftp" to the zone name. -

      -
      +

      -
      -
      -
      +
      +
      +

      Library References

      - -

      +

      As of this writing, there is no formal "manual" for the libraries, except this document, header files (some of which provide pretty detailed explanations), and sample application programs.

      -
      -
      +
      +
      @@ -533,6 +473,6 @@ $ sample-update -a sample-update -k Kxxx.+nnn+mm
      -

      BIND 9.13.2 (Development Release)

      +

      BIND 9.13.3-dev (Development Release)

      diff --git a/doc/arm/Bv9ARM.ch12.html b/doc/arm/Bv9ARM.ch12.html index 6a1658d2c2ffd53c3eeb7cbe967f3b732265e1ee..01926b69f35ff2ed3072249efffde8980cd2c58f 100644 --- a/doc/arm/Bv9ARM.ch12.html +++ b/doc/arm/Bv9ARM.ch12.html @@ -10,7 +10,7 @@ Manual pages - + @@ -151,43 +151,7 @@
      - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
      +
    @@ -206,6 +170,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/Bv9ARM.html b/doc/arm/Bv9ARM.html index 7ee1d9ab93475ebe7604aef1402340a83b8dd5dd..9a030c9ff6c3ae5f346e8a9e93a7aa7df1cbf17c 100644 --- a/doc/arm/Bv9ARM.html +++ b/doc/arm/Bv9ARM.html @@ -10,7 +10,7 @@ BIND 9 Administrator Reference Manual - + @@ -32,7 +32,7 @@

    BIND 9 Administrator Reference Manual

    -

    BIND Version 9.13.2

    +

    BIND Version 9.13.3-dev

    Copyright © 2000-2018 Internet Systems Consortium, Inc. ("ISC")

    @@ -228,13 +228,16 @@
    7. Troubleshooting
    Common Problems
    -
    It's not working; how can I figure out what's wrong?
    +
    +
    It's not working; how can I figure out what's wrong?
    +
    EDNS compliance issues
    +
    Incrementing and Changing the Serial Number
    Where Can I Get Help?
    A. Release Notes
    -
    Release Notes for BIND Version 9.13.2
    +
    Release Notes for BIND Version 9.13.3-dev
    Introduction
    Note on Version Numbering
    @@ -386,32 +389,7 @@
    - - - - - - - - - - - - - - - - - - - - - - - - - -
    +
    @@ -428,6 +406,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/Bv9ARM.pdf b/doc/arm/Bv9ARM.pdf index 429eda9f687593154c7a83212b3097b38e0ab51f..e21bc46f4b81f98ea02c272cd2a9cccfedd58216 100644 Binary files a/doc/arm/Bv9ARM.pdf and b/doc/arm/Bv9ARM.pdf differ diff --git a/doc/arm/man.arpaname.html b/doc/arm/man.arpaname.html index c93a10f54927d383c9e74e6e8960ee03c1607d89..c66ec122c1f08aa29940a6ce99c60508495a975c 100644 --- a/doc/arm/man.arpaname.html +++ b/doc/arm/man.arpaname.html @@ -10,7 +10,7 @@ arpaname - + @@ -32,45 +32,27 @@
    - - - - -
    +

    Name

    -

    - arpaname - — translate IP addresses to the corresponding ARPA names -

    +

    arpaname — translate IP addresses to the corresponding ARPA names

    - - - -
    +

    Synopsis

    -

    - arpaname - {ipaddress ...} -

    -
    - -
    +

    arpaname {ipaddress ...}

    +
    +

    DESCRIPTION

    - -

    +

    arpaname translates IP addresses (IPv4 and IPv6) to the corresponding IN-ADDR.ARPA or IP6.ARPA names.

    -
    - -
    +
    +

    SEE ALSO

    - -

    +

    BIND 9 Administrator Reference Manual.

    -
    - +
    @@ -90,6 +72,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.ddns-confgen.html b/doc/arm/man.ddns-confgen.html index 109465880254026d70bf2c57d59a1541f5628a8c..4dedf5ed4754aa980d911657b3481a23ba068205 100644 --- a/doc/arm/man.ddns-confgen.html +++ b/doc/arm/man.ddns-confgen.html @@ -10,7 +10,7 @@ ddns-confgen - + @@ -32,62 +32,31 @@
    - - - - - -
    +

    Name

    -

    - ddns-confgen - — ddns key generation tool -

    +

    ddns-confgen — ddns key generation tool

    - - - -
    +

    Synopsis

    -

    - tsig-keygen - [-a algorithm] - [-h] - [name] -

    -

    - ddns-confgen - [-a algorithm] - [-h] - [-k keyname] - [-q] - [-r randomfile] - [ - -s name - | -z zone - ] -

    -
    - -
    +

    tsig-keygen [-a algorithm] [-h] [name]

    +

    ddns-confgen [-a algorithm] [-h] [-k keyname] [-q] [-r randomfile] [ -s name | -z zone ]

    +
    +

    DESCRIPTION

    - -

    +

    tsig-keygen and ddns-confgen are invocation methods for a utility that generates keys for use in TSIG signing. The resulting keys can be used, for example, to secure dynamic DNS updates to a zone or for the rndc command channel.

    - -

    +

    When run as tsig-keygen, a domain name can be specified on the command line which will be used as the name of the generated key. If no name is specified, the default is tsig-key.

    - -

    +

    When run as ddns-confgen, the generated key is accompanied by configuration text and instructions that can be used with nsupdate and @@ -97,8 +66,7 @@ rndc-confgen command for setting up command channel security.)

    - -

    +

    Note that named itself can configure a local DDNS key for use with nsupdate -l: it does this when a zone is configured with @@ -108,32 +76,24 @@ if nsupdate is to be used from a remote system.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -a algorithm
    -
    -

    +

    Specifies the algorithm to use for the TSIG key. Available choices are: hmac-md5, hmac-sha1, hmac-sha224, hmac-sha256, hmac-sha384 and hmac-sha512. The default is hmac-sha256. Options are case-insensitive, and the "hmac-" prefix may be omitted. -

    -
    +

    -h
    -
    -

    +

    Prints a short summary of options and arguments. -

    -
    +

    -k keyname
    -
    -

    +

    Specifies the key name of the DDNS authentication key. The default is ddns-key when neither the -s nor -z option is @@ -143,19 +103,15 @@ ddns-key.example.com. The key name must have the format of a valid domain name, consisting of letters, digits, hyphens and periods. -

    -
    +

    -q
    -
    -

    +

    (ddns-confgen only.) Quiet mode: Print only the key, with no explanatory text or usage examples; This is essentially identical to tsig-keygen. -

    -
    +

    -s name
    -
    -

    +

    (ddns-confgen only.) Generate configuration example to allow dynamic updates of a single hostname. The example named.conf @@ -166,11 +122,9 @@ Note that the "self" nametype cannot be used, since the name to be updated may differ from the key name. This option cannot be used with the -z option. -

    -
    +

    -z zone
    -
    -

    +

    (ddns-confgen only.) Generate configuration example to allow dynamic updates of a zone: The example named.conf text @@ -180,27 +134,17 @@ all subdomain names within that zone. This option cannot be used with the -s option. -

    -
    +

    -
    - -
    +
    +

    SEE ALSO

    - -

    - nsupdate(1) - , - - named.conf(5) - , - - named(8) - , +

    nsupdate(1), + named.conf(5), + named(8), BIND 9 Administrator Reference Manual.

    -
    - +
    @@ -220,6 +164,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.delv.html b/doc/arm/man.delv.html index 0b65a52ff3538f4f5ae8bbb637fbf1b064cd8c52..72926e7354be0c30dba881ded9aed69556e36336 100644 --- a/doc/arm/man.delv.html +++ b/doc/arm/man.delv.html @@ -10,7 +10,7 @@ delv - + @@ -32,72 +32,25 @@
    - - - - - -
    +

    Name

    -

    - delv - — DNS lookup and validation utility -

    +

    delv — DNS lookup and validation utility

    - - - -
    +

    Synopsis

    -

    - delv - [@server] - [ - [-4] - | [-6] - ] - [-a anchor-file] - [-b address] - [-c class] - [-d level] - [-i] - [-m] - [-p port#] - [-q name] - [-t type] - [-x addr] - [name] - [type] - [class] - [queryopt...] -

    - -

    - delv - [-h] -

    - -

    - delv - [-v] -

    - -

    - delv - [queryopt...] - [query...] -

    -
    - -
    +

    delv [@server] [[-4] | [-6]] [-a anchor-file] [-b address] [-c class] [-d level] [-i] [-m] [-p port#] [-q name] [-t type] [-x addr] [name] [type] [class] [queryopt...]

    +

    delv [-h]

    +

    delv [-v]

    +

    delv [queryopt...] [query...]

    +
    +

    DESCRIPTION

    - -

    delv +

    delv is a tool for sending DNS queries and validating the results, using the same internal resolver and validator logic as named.

    -

    +

    delv will send to a specified name server all queries needed to fetch and validate the requested data; this includes the original requested query, subsequent queries to follow @@ -107,7 +60,7 @@ behavior of a name server configured for DNSSEC validating and forwarding.

    -

    +

    By default, responses are validated using built-in DNSSEC trust anchor for the root zone ("."). Records returned by delv are either fully validated or @@ -118,7 +71,7 @@ be used to check the validity of DNS responses in environments where local name servers may not be trustworthy.

    -

    +

    Unless it is told to query a specific name server, delv will try each of the servers listed in /etc/resolv.conf. If no usable server @@ -126,18 +79,15 @@ queries to the localhost addresses (127.0.0.1 for IPv4, ::1 for IPv6).

    -

    +

    When no command line arguments or options are given, delv will perform an NS query for "." (the root zone).

    -
    - -
    +
    +

    SIMPLE USAGE

    - - -

    +

    A typical invocation of delv looks like: 

     delv @server name type
    @@ -148,7 +98,7 @@
    server
    -

    +

    is the name or IP address of the name server to query. This can be an IPv4 address in dotted-decimal notation or an IPv6 address in colon-delimited notation. When the supplied @@ -158,7 +108,7 @@ initial lookup is not validated by DNSSEC).

    -

    +

    If no server argument is provided, delv consults /etc/resolv.conf; if an @@ -171,16 +121,13 @@ the localhost addresses (127.0.0.1 for IPv4, ::1 for IPv6).

    -
    +
    name
    -
    -

    +

    is the domain name to be looked up. -

    -
    +

    type
    -
    -

    +

    indicates what type of query is required — ANY, A, MX, etc. type can be any valid query @@ -188,27 +135,23 @@ type argument is supplied, delv will perform a lookup for an A record. -

    -
    +

    - -
    - -
    +
    +

    OPTIONS

    - -
    +
    -a anchor-file
    -

    +

    Specifies a file from which to read DNSSEC trust anchors. The default is /etc/bind.keys, which is included with BIND 9 and contains one or more trust anchors for the root zone (".").

    -

    +

    Keys that do not match the root zone name are ignored. An alternate key name can be specified using the +root=NAME options. DNSSEC Lookaside @@ -216,7 +159,7 @@ +dlv=NAME to specify the name of a zone containing DLV records.

    -

    +

    Note: When reading the trust anchor file, delv treats managed-keys statements and trusted-keys statements @@ -230,28 +173,23 @@ /etc/bind.keys to use DNSSEC validation in delv.

    -
    +
    -b address
    -
    -

    +

    Sets the source IP address of the query to address. This must be a valid address on one of the host's network interfaces or "0.0.0.0" or "::". An optional source port may be specified by appending "#<port>" -

    -
    +

    -c class
    -
    -

    +

    Sets the query class for the requested data. Currently, only class "IN" is supported in delv and any other value is ignored. -

    -
    +

    -d level
    -
    -

    +

    Set the systemwide debug level to level. The allowed range is from 0 to 99. The default is 0 (no debugging). @@ -260,17 +198,13 @@ See the +mtrace, +rtrace, and +vtrace options below for additional debugging details. -

    -
    +

    -h
    -
    -

    +

    Display the delv help usage output and exit. -

    -
    +

    -i
    -
    -

    +

    Insecure mode. This disables internal DNSSEC validation. (Note, however, this does not set the CD bit on upstream queries. If the server being queried is performing DNSSEC @@ -278,37 +212,30 @@ can cause delv to time out. When it is necessary to examine invalid data to debug a DNSSEC problem, use dig +cd.) -

    -
    +

    -m
    -
    -

    +

    Enables memory usage debugging. -

    -
    +

    -p port#
    -
    -

    +

    Specifies a destination port to use for queries instead of the standard DNS port number 53. This option would be used with a name server that has been configured to listen for queries on a non-standard port number. -

    -
    +

    -q name
    -
    -

    +

    Sets the query name to name. While the query name can be specified without using the -q, it is sometimes necessary to disambiguate names from types or classes (for example, when looking up the name "ns", which could be misinterpreted as the type NS, or "ch", which could be misinterpreted as class CH). -

    -
    +

    -t type
    -

    +

    Sets the query type to type, which can be any valid query type supported in BIND 9 except for zone transfer types AXFR and IXFR. As with @@ -316,21 +243,18 @@ query name type or class when they are ambiguous. it is sometimes necessary to disambiguate names from types.

    -

    +

    The default query type is "A", unless the -x option is supplied to indicate a reverse lookup, in which case it is "PTR".

    -
    +
    -v
    -
    -

    +

    Print the delv version and exit. -

    -
    +

    -x addr
    -
    -

    +

    Performs a reverse lookup, mapping an addresses to a name. addr is an IPv4 address in dotted-decimal notation, or a colon-delimited IPv6 address. @@ -340,33 +264,24 @@ lookup for a name like 11.12.13.10.in-addr.arpa and sets the query type to PTR. IPv6 addresses are looked up using nibble format under the IP6.ARPA domain. -

    -
    +

    -4
    -
    -

    +

    Forces delv to only use IPv4. -

    -
    +

    -6
    -
    -

    +

    Forces delv to only use IPv6. -

    -
    +

    -
    - -
    +
    +

    QUERY OPTIONS

    - - -

    delv +

    delv provides a number of query options which affect the way results are displayed, and in some cases the way lookups are performed.

    - -

    +

    Each query option is identified by a keyword preceded by a plus sign (+). Some keywords set or reset an option. These may be preceded by the string @@ -378,8 +293,7 @@

    +[no]cdflag
    -
    -

    +

    Controls whether to set the CD (checking disabled) bit in queries sent by delv. This may be useful when troubleshooting DNSSEC problems from behind a validating @@ -388,25 +302,20 @@ the CD flag on queries will cause the resolver to return invalid responses, which delv can then validate internally and report the errors in detail. -

    -
    +

    +[no]class
    -
    -

    +

    Controls whether to display the CLASS when printing a record. The default is to display the CLASS. -

    -
    +

    +[no]ttl
    -
    -

    +

    Controls whether to display the TTL when printing a record. The default is to display the TTL. -

    -
    +

    +[no]rtrace
    -

    +

    Toggle resolver fetch logging. This reports the name and type of each query sent by delv in the process of carrying out the resolution and validation @@ -414,69 +323,62 @@ all subsequent queries to follow CNAMEs and to establish a chain of trust for DNSSEC validation.

    -

    +

    This is equivalent to setting the debug level to 1 in the "resolver" logging category. Setting the systemwide debug level to 1 using the -d option will product the same output (but will affect other logging categories as well).

    -
    +
    +[no]mtrace
    -

    +

    Toggle message logging. This produces a detailed dump of the responses received by delv in the process of carrying out the resolution and validation process.

    -

    +

    This is equivalent to setting the debug level to 10 for the "packets" module of the "resolver" logging category. Setting the systemwide debug level to 10 using the -d option will produce the same output (but will affect other logging categories as well).

    -
    +
    +[no]vtrace
    -

    +

    Toggle validation logging. This shows the internal process of the validator as it determines whether an answer is validly signed, unsigned, or invalid.

    -

    +

    This is equivalent to setting the debug level to 3 for the "validator" module of the "dnssec" logging category. Setting the systemwide debug level to 3 using the -d option will produce the same output (but will affect other logging categories as well).

    -
    +
    +[no]short
    -
    -

    +

    Provide a terse answer. The default is to print the answer in a verbose form. -

    -
    +

    +[no]comments
    -
    -

    +

    Toggle the display of comment lines in the output. The default is to print comments. -

    -
    +

    +[no]rrcomments
    -
    -

    +

    Toggle the display of per-record comments in the output (for example, human-readable key information about DNSKEY records). The default is to print per-record comments. -

    -
    +

    +[no]crypto
    -
    -

    +

    Toggle the display of cryptographic fields in DNSSEC records. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing them makes it easier to see @@ -484,18 +386,14 @@ When omitted they are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e.g. "[ key id = value ]". -

    -
    +

    +[no]trust
    -
    -

    +

    Controls whether to display the trust level when printing a record. The default is to display the trust level. -

    -
    +

    +[no]split[=W]
    -
    -

    +

    Split long hex- or base64-formatted fields in resource records into chunks of W characters (where W is rounded up to the nearest @@ -504,30 +402,24 @@ +split=0 causes fields not to be split at all. The default is 56 characters, or 44 characters when multiline mode is active. -

    -
    +

    +[no]all
    -
    -

    +

    Set or clear the display options +[no]comments, +[no]rrcomments, and +[no]trust as a group. -

    -
    +

    +[no]multiline
    -
    -

    +

    Print long records (such as RRSIG, DNSKEY, and SOA records) in a verbose multi-line format with human-readable comments. The default is to print each record on a single line, to facilitate machine parsing of the delv output. -

    -
    +

    +[no]dnssec
    -
    -

    +

    Indicates whether to display RRSIG records in the delv output. The default is to do so. Note that (unlike in dig) @@ -537,11 +429,9 @@ will always occur unless suppressed by the use of -i or +noroot and +nodlv. -

    -
    +

    +[no]root[=ROOT]
    -
    -

    +

    Indicates whether to perform conventional (non-lookaside) DNSSEC validation, and if so, specifies the name of a trust anchor. The default is to validate using @@ -549,63 +439,47 @@ a built-in key. If specifying a different trust anchor, then -a must be used to specify a file containing the key. -

    -
    +

    +[no]dlv[=DLV]
    -
    -

    +

    Indicates whether to perform DNSSEC lookaside validation, and if so, specifies the name of the DLV trust anchor. The -a option must also be used to specify a file containing the DLV key. -

    -
    +

    +[no]tcp
    -
    -

    +

    Controls whether to use TCP when sending queries. The default is to use UDP unless a truncated response has been received. -

    -
    +

    +[no]unknownformat
    -
    -

    +

    Print all RDATA in unknown RR type presentation format (RFC 3597). The default is to print RDATA for known types in the type's presentation format. -

    -
    +

    -
    - -
    +
    +

    FILES

    - -

    /etc/bind.keys

    -

    /etc/resolv.conf

    -
    - -
    +

    /etc/bind.keys

    +

    /etc/resolv.conf

    +
    +

    SEE ALSO

    - -

    - dig(1) - , - - named(8) - , +

    dig(1), + named(8), RFC4034, RFC4035, RFC4431, RFC5074, RFC5155.

    -
    - +
    @@ -625,6 +499,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dig.html b/doc/arm/man.dig.html index b7783a3f038a2c5b9a9d501267b77e2a29fe4cab..bcee8a364c70a4899c8cd6dd537b4d97efc4ae01 100644 --- a/doc/arm/man.dig.html +++ b/doc/arm/man.dig.html @@ -10,7 +10,7 @@ dig - + @@ -32,63 +32,19 @@
    - - - - - -
    +

    Name

    -

    - dig - — DNS lookup utility -

    +

    dig — DNS lookup utility

    - - - -
    +

    Synopsis

    -

    - dig - [@server] - [-b address] - [-c class] - [-f filename] - [-k filename] - [-m] - [-p port#] - [-q name] - [-t type] - [-v] - [-x addr] - [-y [hmac:]name:key] - [ - [-4] - | [-6] - ] - [name] - [type] - [class] - [queryopt...] -

    - -

    - dig - [-h] -

    - -

    - dig - [global-queryopt...] - [query...] -

    -
    - -
    +

    dig [@server] [-b address] [-c class] [-f filename] [-k filename] [-m] [-p port#] [-q name] [-t type] [-v] [-x addr] [-y [hmac:]name:key] [[-4] | [-6]] [name] [type] [class] [queryopt...]

    +

    dig [-h]

    +

    dig [global-queryopt...] [query...]

    +
    +

    DESCRIPTION

    - -

    dig is a flexible tool +

    dig is a flexible tool for interrogating DNS name servers. It performs DNS lookups and displays the answers that are returned from the name server(s) that were queried. Most DNS administrators use dig to @@ -96,8 +52,7 @@ clarity of output. Other lookup tools tend to have less functionality than dig.

    - -

    +

    Although dig is normally used with command-line arguments, it also has a batch mode of operation for reading lookup @@ -108,42 +63,34 @@ from the command line.

    - -

    +

    Unless it is told to query a specific name server, dig will try each of the servers listed in /etc/resolv.conf. If no usable server addresses are found, dig will send the query to the local host.

    - -

    +

    When no command line arguments or options are given, dig will perform an NS query for "." (the root).

    - -

    +

    It is possible to set per-user defaults for dig via ${HOME}/.digrc. This file is read and any options in it are applied before the command line arguments.

    - -

    +

    The IN and CH class names overlap with the IN and CH top level domain names. Either use the -t and -c options to specify the type and class, use the -q the specify the domain name, or use "IN." and "CH." when looking up these top level domains.

    - -
    - -
    +
    +

    SIMPLE USAGE

    - - -

    +

    A typical invocation of dig looks like: 

     dig @server name type
    @@ -154,7 +101,7 @@
    server
    -

    +

    is the name or IP address of the name server to query. This can be an IPv4 address in dotted-decimal notation or an IPv6 address in colon-delimited notation. When the supplied @@ -162,7 +109,7 @@ dig resolves that name before querying that name server.

    -

    +

    If no server argument is provided, dig consults /etc/resolv.conf; if an @@ -175,16 +122,13 @@ local host. The reply from the name server that responds is displayed.

    -
    +
    name
    -
    -

    +

    is the name of the resource record that is to be looked up. -

    -
    +

    type
    -
    -

    +

    indicates what type of query is required — ANY, A, MX, SIG, etc. type can be any valid query @@ -192,109 +136,82 @@ type argument is supplied, dig will perform a lookup for an A record. -

    -
    +

    - -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -4
    -
    -

    +

    Use IPv4 only. -

    -
    +

    -6
    -
    -

    +

    Use IPv6 only. -

    -
    +

    -b address[#port]
    -
    -

    +

    Set the source IP address of the query. The address must be a valid address on one of the host's network interfaces, or "0.0.0.0" or "::". An optional port may be specified by appending "#<port>" -

    -
    +

    -c class
    -
    -

    +

    Set the query class. The default class is IN; other classes are HS for Hesiod records or CH for Chaosnet records. -

    -
    +

    -f file
    -
    -

    +

    Batch mode: dig reads a list of lookup requests to process from the given file. Each line in the file should be organized in the same way they would be presented as queries to dig using the command-line interface. -

    -
    +

    -i
    -
    -

    +

    Do reverse IPv6 lookups using the obsolete RFC 1886 IP6.INT domain, which is no longer in use. Obsolete bit string label queries (RFC 2874) are not attempted. -

    -
    +

    -k keyfile
    -
    -

    +

    Sign queries using TSIG using a key read from the given file. Key files can be generated using - - tsig-keygen(8) - . + tsig-keygen(8). When using TSIG authentication with dig, the name server that is queried needs to know the key and algorithm that is being used. In BIND, this is done by providing appropriate key and server statements in named.conf. -

    -
    +

    -m
    -
    -

    +

    Enable memory usage debugging. -

    -
    +

    -p port
    -
    -

    +

    Send the query to a non-standard port on the server, instead of the default port 53. This option would be used to test a name server that has been configured to listen for queries on a non-standard port number. -

    -
    +

    -q name
    -
    -

    +

    The domain name to query. This is useful to distinguish the name from other arguments. -

    -
    +

    -t type
    -

    +

    The resource record type to query. It can be any valid query type. If it is a resource record type supported in BIND 9, it can be given by the type mnemonic (such as "NS" or "AAAA"). @@ -308,28 +225,23 @@ record was N.

    -

    +

    All resource record types can be expressed as "TYPEnn", where "nn" is the number of the type. If the resource record type is not supported in BIND 9, the result will be displayed as described in RFC 3597.

    -
    +
    -u
    -
    -

    +

    Print query times in microseconds instead of milliseconds. -

    -
    +

    -v
    -
    -

    +

    Print the version number and exit. -

    -
    +

    -x addr
    -
    -

    +

    Simplified reverse lookups, for mapping addresses to names. The addr is an IPv4 address in dotted-decimal notation, or a colon-delimited IPv6 @@ -344,11 +256,10 @@ addresses are looked up using nibble format under the IP6.ARPA domain (but see also the -i option). -

    -
    +

    -y [hmac:]keyname:secret
    -

    +

    Sign queries using TSIG with the given authentication key. keyname is the name of the key, and secret is the base64 encoded shared secret. @@ -360,34 +271,28 @@ is not specified, the default is hmac-md5 or if MD5 was disabled hmac-sha256.

    -

    +

    NOTE: You should use the -k option and avoid the -y option, because with -y the shared secret is supplied as a command line argument in clear text. This may be visible in the output from - - ps(1) - + ps(1) or in a history file maintained by the user's shell.

    -
    +
    -
    - -
    +
    +

    QUERY OPTIONS

    - - -

    dig +

    dig provides a number of query options which affect the way in which lookups are made and the results displayed. Some of these set or reset flag bits in the query header, some determine which sections of the answer get printed, and others determine the timeout and retry strategies.

    - -

    +

    Each query option is identified by a keyword preceded by a plus sign (+). Some keywords set or reset an option. These may be preceded @@ -403,27 +308,20 @@

    +[no]aaflag
    -
    -

    +

    A synonym for +[no]aaonly. -

    -
    +

    +[no]aaonly
    -
    -

    +

    Sets the "aa" flag in the query. -

    -
    +

    +[no]additional
    -
    -

    +

    Display [do not display] the additional section of a reply. The default is to display it. -

    -
    +

    +[no]adflag
    -
    -

    +

    Set [do not set] the AD (authentic data) bit in the query. This requests the server to return whether all of the answer and authority sections have all @@ -433,102 +331,80 @@ from a OPT-OUT range. AD=0 indicate that some part of the answer was insecure or not validated. This bit is set by default. -

    -
    +

    +[no]all
    -
    -

    +

    Set or clear all display flags. -

    -
    +

    +[no]answer
    -
    -

    +

    Display [do not display] the answer section of a reply. The default is to display it. -

    -
    +

    +[no]authority
    -
    -

    +

    Display [do not display] the authority section of a reply. The default is to display it. -

    -
    +

    +[no]badcookie
    -
    -

    +

    Retry lookup with the new server cookie if a BADCOOKIE response is received. -

    -
    +

    +[no]besteffort
    -
    -

    +

    Attempt to display the contents of messages which are malformed. The default is to not display malformed answers. -

    -
    +

    +bufsize=B
    -
    -

    +

    Set the UDP message buffer size advertised using EDNS0 to B bytes. The maximum and minimum sizes of this buffer are 65535 and 0 respectively. Values outside this range are rounded up or down appropriately. Values other than zero will cause a EDNS query to be sent. -

    -
    +

    +[no]cdflag
    -
    -

    +

    Set [do not set] the CD (checking disabled) bit in the query. This requests the server to not perform DNSSEC validation of responses. -

    -
    +

    +[no]class
    -
    -

    +

    Display [do not display] the CLASS when printing the record. -

    -
    +

    +[no]cmd
    -
    -

    +

    Toggles the printing of the initial comment in the output identifying the version of dig and the query options that have been applied. This comment is printed by default. -

    -
    +

    +[no]comments
    -
    -

    +

    Toggle the display of comment lines in the output. The default is to print comments. -

    -
    +

    +[no]cookie[=####]
    -

    +

    Send a COOKIE EDNS option, with optional value. Replaying a COOKIE from a previous response will allow the server to identify a previous client. The default is +cookie.

    -

    +

    +cookie is also set when +trace is set to better emulate the default queries from a nameserver.

    -
    +
    +[no]crypto
    -
    -

    +

    Toggle the display of cryptographic fields in DNSSEC records. The contents of these field are unnecessary to debug most DNSSEC validation failures and removing @@ -537,71 +413,55 @@ are replaced by the string "[omitted]" or in the DNSKEY case the key id is displayed as the replacement, e.g. "[ key id = value ]". -

    -
    +

    +[no]defname
    -
    -

    +

    Deprecated, treated as a synonym for +[no]search -

    -
    +

    +[no]dnssec
    -
    -

    +

    Requests DNSSEC records be sent by setting the DNSSEC OK bit (DO) in the OPT record in the additional section of the query. -

    -
    +

    +domain=somename
    -
    -

    +

    Set the search list to contain the single domain somename, as if specified in a domain directive in /etc/resolv.conf, and enable search list processing as if the +search option were given. -

    -
    +

    +dscp=value
    -
    -

    +

    Set the DSCP code point to be used when sending the query. Valid DSCP code points are in the range [0..63]. By default no code point is explicitly set. -

    -
    +

    +[no]edns[=#]
    -
    -

    +

    Specify the EDNS version to query with. Valid values are 0 to 255. Setting the EDNS version will cause a EDNS query to be sent. +noedns clears the remembered EDNS version. EDNS is set to 0 by default. -

    -
    +

    +[no]ednsflags[=#]
    -
    -

    +

    Set the must-be-zero EDNS flags bits (Z bits) to the specified value. Decimal, hex and octal encodings are accepted. Setting a named flag (e.g. DO) will silently be ignored. By default, no Z bits are set. -

    -
    +

    +[no]ednsnegotiation
    -
    -

    +

    Enable / disable EDNS version negotiation. By default EDNS version negotiation is enabled. -

    -
    +

    +[no]ednsopt[=code[:value]]
    -
    -

    +

    Specify EDNS option with code point code and optionally payload of value as a hexadecimal string. code can be @@ -609,98 +469,74 @@ NSID or ECS), or an arbitrary numeric value. +noednsopt clears the EDNS options to be sent. -

    -
    +

    +[no]expire
    -
    -

    +

    Send an EDNS Expire option. -

    -
    +

    +[no]fail
    -
    -

    +

    Do not try the next server if you receive a SERVFAIL. The default is to not try the next server which is the reverse of normal stub resolver behavior. -

    -
    +

    +[no]header-only
    -
    -

    +

    Send a query with a DNS header without a question section. The default is to add a question section. The query type and query name are ignored when this is set. -

    -
    +

    +[no]identify
    -
    -

    +

    Show [or do not show] the IP address and port number that supplied the answer when the +short option is enabled. If short form answers are requested, the default is not to show the source address and port number of the server that provided the answer. -

    -
    +

    +[no]idnin
    -
    -

    +

    Process [do not process] IDN domain names on input. This requires IDN SUPPORT to have been enabled at compile time. The default is to process IDN input. -

    -
    +

    +[no]idnout
    -
    -

    +

    Convert [do not convert] puny code on output. This requires IDN SUPPORT to have been enabled at compile time. The default is to convert output. -

    -
    +

    +[no]ignore
    -
    -

    +

    Ignore truncation in UDP responses instead of retrying with TCP. By default, TCP retries are performed. -

    -
    +

    +[no]keepalive
    -
    -

    +

    Send [or do not send] an EDNS Keepalive option. -

    -
    +

    +[no]keepopen
    -
    -

    +

    Keep the TCP socket open between queries and reuse it rather than creating a new TCP socket for each lookup. The default is +nokeepopen. -

    -
    +

    +[no]mapped
    -
    -

    +

    Allow mapped IPv4 over IPv6 addresses to be used. The default is +mapped. -

    -
    +

    +[no]multiline
    -
    -

    +

    Print records like the SOA records in a verbose multi-line format with human-readable comments. The default is to print each record on a single line, to facilitate machine parsing of the dig output. -

    -
    +

    +ndots=D
    -
    -

    +

    Set the number of dots that have to appear in name to D for it to be considered absolute. The default value @@ -712,44 +548,34 @@ or domain directive in /etc/resolv.conf if +search is set. -

    -
    +

    +[no]nsid
    -
    -

    +

    Include an EDNS name server ID request when sending a query. -

    -
    +

    +[no]nssearch
    -
    -

    +

    When this option is set, dig attempts to find the authoritative name servers for the zone containing the name being looked up and display the SOA record that each name server has for the zone. Addresses of servers that that did not respond are also printed. -

    -
    +

    +[no]onesoa
    -
    -

    +

    Print only one (starting) SOA record when performing an AXFR. The default is to print both the starting and ending SOA records. -

    -
    +

    +[no]opcode=value
    -
    -

    +

    Set [restore] the DNS message opcode to the specified value. The default value is QUERY (0). -

    -
    +

    +padding=value
    -
    -

    +

    Pad the size of the query packet using the EDNS Padding option to blocks of value bytes. For example, +padding=32 would cause a 48-byte query to @@ -759,106 +585,84 @@ however, this is not mandatory. Responses to padded queries may also be padded, but only if the query uses TCP or DNS COOKIE. -

    -
    +

    +[no]qr
    -
    -

    +

    Print [do not print] the query as it is sent. By default, the query is not printed. -

    -
    +

    +[no]question
    -
    -

    +

    Print [do not print] the question section of a query when an answer is returned. The default is to print the question section as a comment. -

    -
    +

    +[no]raflag
    -
    -

    +

    Set [do not set] the RA (Recursion Available) bit in the query. The default is +noraflag. This bit should be ignored by the server for QUERY. -

    -
    +

    +[no]rdflag
    -
    -

    +

    A synonym for +[no]recurse. -

    -
    +

    +[no]recurse
    -
    -

    +

    Toggle the setting of the RD (recursion desired) bit in the query. This bit is set by default, which means dig normally sends recursive queries. Recursion is automatically disabled when the +nssearch or +trace query options are used. -

    -
    +

    +retry=T
    -
    -

    +

    Sets the number of times to retry UDP queries to server to T instead of the default, 2. Unlike +tries, this does not include the initial query. -

    -
    +

    +[no]rrcomments
    -
    -

    +

    Toggle the display of per-record comments in the output (for example, human-readable key information about DNSKEY records). The default is not to print record comments unless multiline mode is active. -

    -
    +

    +[no]search
    -

    +

    Use [do not use] the search list defined by the searchlist or domain directive in resolv.conf (if any). The search list is not used by default.

    -

    +

    'ndots' from resolv.conf (default 1) which may be overridden by +ndots determines if the name will be treated as relative or not and hence whether a search is eventually performed or not.

    -
    +
    +[no]short
    -
    -

    +

    Provide a terse answer. The default is to print the answer in a verbose form. -

    -
    +

    +[no]showsearch
    -
    -

    +

    Perform [do not perform] a search showing intermediate results. -

    -
    +

    +[no]sigchase
    -
    -

    +

    This feature is now obsolete and has been removed; use delv instead. -

    -
    +

    +split=W
    -
    -

    +

    Split long hex- or base64-formatted fields in resource records into chunks of W characters (where W is rounded @@ -867,24 +671,21 @@ +split=0 causes fields not to be split at all. The default is 56 characters, or 44 characters when multiline mode is active. -

    -
    +

    +[no]stats
    -
    -

    +

    This query option toggles the printing of statistics: when the query was made, the size of the reply and so on. The default behavior is to print the query statistics. -

    -
    +

    +[no]subnet=addr[/prefix-length]
    -

    +

    Send (don't send) an EDNS Client Subnet option with the specified IP address or network prefix.

    -

    +

    dig +subnet=0.0.0.0/0, or simply dig +subnet=0 for short, sends an EDNS CLIENT-SUBNET option with an empty address and a source @@ -893,28 +694,23 @@ not be used when resolving this query.

    -
    +
    +[no]tcflag
    -
    -

    +

    Set [do not set] the TC (TrunCation) bit in the query. The default is +notcflag. This bit should be ignored by the server for QUERY. -

    -
    +

    +[no]tcp
    -
    -

    +

    Use [do not use] TCP when querying name servers. The default behavior is to use UDP unless a type any or ixfr=N query is requested, in which case the default is TCP. AXFR queries always use TCP. -

    -
    +

    +timeout=T
    -
    -

    +

    Sets the timeout for a query to T seconds. The default @@ -922,19 +718,16 @@ An attempt to set T to less than 1 will result in a query timeout of 1 second being applied. -

    -
    +

    +[no]topdown
    -
    -

    +

    This feature is related to dig +sigchase, which is obsolete and has been removed. Use delv instead. -

    -
    +

    +[no]trace
    -

    +

    Toggle tracing of the delegation path from the root name servers for the name being looked up. Tracing is disabled by default. When tracing is enabled, @@ -942,84 +735,69 @@ resolve the name being looked up. It will follow referrals from the root servers, showing the answer from each server that was used to resolve the lookup. -

    +

    +

    If @server is also specified, it affects only the initial query for the root zone name servers. -

    +

    +

    +dnssec is also set when +trace is set to better emulate the default queries from a nameserver.

    -
    +
    +tries=T
    -
    -

    +

    Sets the number of times to try UDP queries to server to T instead of the default, 3. If T is less than or equal to zero, the number of tries is silently rounded up to 1. -

    -
    +

    +trusted-key=####
    -
    -

    +

    Formerly specified trusted keys for use with dig +sigchase. This feature is now obsolete and has been removed; use delv instead. -

    -
    +

    +[no]ttlid
    -
    -

    +

    Display [do not display] the TTL when printing the record. -

    -
    +

    +[no]ttlunits
    -
    -

    +

    Display [do not display] the TTL in friendly human-readable time units of "s", "m", "h", "d", and "w", representing seconds, minutes, hours, days and weeks. Implies +ttlid. -

    -
    +

    +[no]unknownformat
    -
    -

    +

    Print all RDATA in unknown RR type presentation format (RFC 3597). The default is to print RDATA for known types in the type's presentation format. -

    -
    +

    +[no]vc
    -
    -

    +

    Use [do not use] TCP when querying name servers. This alternate syntax to +[no]tcp is provided for backwards compatibility. The "vc" stands for "virtual circuit". -

    -
    +

    +[no]zflag
    -
    -

    +

    Set [do not set] the last unassigned DNS header flag in a DNS query. This flag is off by default. -

    -
    +

    -
    - -
    +
    +

    MULTIPLE QUERIES

    - - -

    +

    The BIND 9 implementation of dig supports specifying multiple queries on the command line (in addition to @@ -1027,8 +805,7 @@ queries can be supplied with its own set of flags, options and query options.

    - -

    +

    In this case, each query argument represent an individual query in the command-line syntax described above. Each @@ -1036,8 +813,7 @@ looked up, an optional query type and class and any query options that should be applied to that query.

    - -

    +

    A global set of query options, which should be applied to all queries, can also be supplied. These global query options must precede the first tuple of name, class, type, options, flags, and query options @@ -1065,13 +841,10 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr will not print the initial query when it looks up the NS records for isc.org.

    - -
    - -
    +
    +

    IDN SUPPORT

    - -

    +

    If dig has been built with IDN (internationalized domain name) support, it can accept and display non-ASCII domain names. dig appropriately converts character encoding of @@ -1081,44 +854,29 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr parameters +noidnin and +noidnout.

    -
    - -
    +
    +

    FILES

    - -

    /etc/resolv.conf +

    /etc/resolv.conf

    -

    ${HOME}/.digrc +

    ${HOME}/.digrc

    -
    - -
    +
    +

    SEE ALSO

    - -

    - delv(1) - , - - host(1) - , - - named(8) - , - - dnssec-keygen(8) - , +

    delv(1), + host(1), + named(8), + dnssec-keygen(8), RFC 1035.

    -
    - -
    +
    +

    BUGS

    - -

    +

    There are probably too many query options.

    -
    - +
    @@ -1138,6 +896,6 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-cds.html b/doc/arm/man.dnssec-cds.html index ad5a7d57337335395261ec699312bed51077bcf5..c45543c4c97b39b769003f9b759d20ab39a5af75 100644 --- a/doc/arm/man.dnssec-cds.html +++ b/doc/arm/man.dnssec-cds.html @@ -10,7 +10,7 @@ dnssec-cds - + @@ -32,44 +32,17 @@
    - - - - - -
    +

    Name

    -

    - dnssec-cds - — change DS records for a child zone based on CDS/CDNSKEY -

    +

    dnssec-cds — change DS records for a child zone based on CDS/CDNSKEY

    - - - -
    +

    Synopsis

    -

    - dnssec-cds - [-a alg...] - [-c class] - [-D] - {-d dsset-file} - {-f child-file} - [-i [extension]] - [-s start-time] - [-T ttl] - [-u] - [-v level] - [-V] - {domain} -

    -
    - -
    +

    dnssec-cds [-a alg...] [-c class] [-D] {-d dsset-file} {-f child-file} [-i [extension]] [-s start-time] [-T ttl] [-u] [-v level] [-V] {domain}

    +
    +

    DESCRIPTION

    - -

    +

    The dnssec-cds command changes DS records at a delegation point based on CDS or CDNSKEY records published in the child zone. If both CDS and CDNSKEY records are present in @@ -79,7 +52,7 @@ parent can keep the DS records up to date and enable automatic rolling of KSKs.

    -

    +

    Two input files are required. The -f child-file option specifies a file containing the child's CDS and/or CDNSKEY @@ -92,27 +65,27 @@ dnssec-dsfromkey, or the output of a previous run of dnssec-cds.

    -

    +

    The dnssec-cds command uses special DNSSEC validation logic specified by RFC 7344. It requires that the CDS and/or CDNSKEY records are validly signed by a key represented in the existing DS records. This will typicially be the pre-existing key-signing key (KSK).

    -

    +

    For protection against replay attacks, the signatures on the child records must not be older than they were on a previous run of dnssec-cds. This time is obtained from the modification time of the dsset- file, or from the -s option.

    -

    +

    To protect against breaking the delegation, dnssec-cds ensures that the DNSKEY RRset can be verified by every key algorithm in the new DS RRset, and that the same set of keys are covered by every DS digest type.

    -

    +

    By default, replacement DS records are written to the standard output; with the -i option the input file is overwritten in place. The replacement DS records will be the @@ -120,56 +93,49 @@ output can be empty if the CDS / CDNSKEY records specify that the child zone wants to go insecure.

    -

    +

    Warning: Be careful not to delete the DS records when dnssec-cds fails!

    -

    +

    Alternatively, dnssec-cds -u writes an nsupdate script to the standard output. You can use the -u and -i options together to maintain a dsset- file as well as emit an nsupdate script.

    - -
    - -
    +
    +

    OPTIONS

    - -
    +
    -a algorithm
    -

    +

    Specify a digest algorithm to use when converting CDNSKEY records to DS records. This option can be repeated, so that multiple DS records are created for each CDNSKEY record. This option has no effect when using CDS records.

    -

    +

    The algorithm must be one of SHA-1 (SHA1), SHA-256 (SHA256), or SHA-384 (SHA384). These values are case insensitive. If no algorithm is specified, the default is SHA-256.

    -
    +
    -c class
    -
    -

    +

    Specifies the DNS class of the zones. -

    -
    +

    -D
    -
    -

    +

    Generate DS records from CDNSKEY records if both CDS and CDNSKEY records are present in the child zone. By default CDS records are preferred. -

    -
    +

    -d path
    -

    +

    Location of the parent DS records. The path can be the name of a file containing the DS records, or if it is a @@ -177,31 +143,31 @@ a dsset- file for the domain inside the directory.

    -

    +

    To protect against replay attacks, child records are rejected if they were signed earlier than the modification time of the dsset- file. This can be adjusted with the -s option.

    -
    +
    -f child-file
    -

    +

    File containing the child's CDS and/or CDNSKEY records, plus its DNSKEY records and the covering RRSIG records so that they can be authenticated.

    -

    +

    The EXAMPLES below describe how to generate this file.

    -
    +
    -i[extension]
    -

    +

    Update the dsset- file in place, instead of writing DS records to the standard output.

    -

    +

    There must be no space between the -i and the extension. If you provide no extension then the @@ -211,17 +177,17 @@ with the extension appended to its filename.

    -

    +

    To protect against replay attacks, the modification time of the dsset- file is set to match the signature inception time of the child records, provided that is later than the file's current modification time.

    -
    +
    -s start-time
    -

    +

    Specify the date and time after which RRSIG records become acceptable. This can be either an absolute or relative time. An absolute start time is indicated by a number in @@ -231,82 +197,69 @@ which is N seconds before the file modification time. A time relative to the current time is indicated with now+N.

    -

    +

    If no start-time is specified, the modification time of the dsset- file is used.

    -
    +
    -T ttl
    -
    -

    +

    Specifies a TTL to be used for new DS records. If not specified, the default is the TTL of the old DS records. If they had no explicit TTL then the new DS records also have no explicit TTL. -

    -
    +

    -u
    -

    +

    Write an nsupdate script to the standard output, instead of printing the new DS reords. The output will be empty if no change is needed.

    -

    +

    Note: The TTL of new records needs to be specified, either in the original dsset- file, or with the -T option, or using the nsupdate ttl command.

    -
    +
    -V
    -
    -

    +

    Print version information. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. Level 1 is intended to be usefully verbose for general users; higher levels are intended for developers. -

    -
    +

    domain
    -
    -

    +

    The name of the delegation point / child zone apex. -

    -
    +

    -
    - -
    +
    +

    EXIT STATUS

    - -

    +

    The dnssec-cds command exits 0 on success, or non-zero if an error occurred.

    -

    +

    In the success case, the DS records might or might not need to be changed.

    - -
    - -
    +
    +

    EXAMPLES

    - -

    +

    Before running dnssec-signzone, you can ensure that the delegations are up-to-date by running dnssec-cds on every dsset- file.

    -

    +

    To fetch the child records required by dnssec-cds you can invoke dig as in the script below. It's okay if the dig fails since @@ -319,8 +272,7 @@ do dnssec-cds -i -f /dev/stdin -d $f $d done - -

    +

    When the parent zone is automatically signed by named, you can use dnssec-cds with nsupdate to maintain a delegation as follows. @@ -333,30 +285,18 @@ dig +dnssec +noall +answer $d DNSKEY $d CDNSKEY $d CDS | dnssec-cds -u -i -f /dev/stdin -d $f $d | nsupdate -l -

    - -
    +
    +

    SEE ALSO

    - -

    - - dig(1) - , - - dnssec-settime(8) - , - - dnssec-signzone(8) - , - - nsupdate(1) - , +

    + dig(1), + dnssec-settime(8), + dnssec-signzone(8), + nsupdate(1), BIND 9 Administrator Reference Manual, RFC 7344.

    - -
    - +
    @@ -376,6 +316,6 @@ nsupdate -l
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-checkds.html b/doc/arm/man.dnssec-checkds.html index d62f72db56199ef0046142080e9726f52ff24b52..ac61037e1e5a625c5e0dc397c327c9225366c8d3 100644 --- a/doc/arm/man.dnssec-checkds.html +++ b/doc/arm/man.dnssec-checkds.html @@ -10,7 +10,7 @@ dnssec-checkds - + @@ -32,104 +32,61 @@
    - - - - - -
    +

    Name

    -

    - dnssec-checkds - — DNSSEC delegation consistency checking tool -

    +

    dnssec-checkds — DNSSEC delegation consistency checking tool

    - - - -
    +

    Synopsis

    -

    - dnssec-checkds - [-d dig path] - [-D dsfromkey path] - [-f file] - [-l domain] - [-s file] - {zone} -

    -
    - -
    +

    dnssec-checkds [-d dig path] [-D dsfromkey path] [-f file] [-l domain] [-s file] {zone}

    +
    +

    DESCRIPTION

    - -

    dnssec-checkds +

    dnssec-checkds verifies the correctness of Delegation Signer (DS) or DNSSEC Lookaside Validation (DLV) resource records for keys in a specified zone.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -f file
    -
    -

    +

    If a file is specified, then the zone is read from that file to find the DNSKEY records. If not, then the DNSKEY records for the zone are looked up in the DNS. -

    -
    +

    -l domain
    -
    -

    +

    Check for a DLV record in the specified lookaside domain, instead of checking for a DS record in the zone's parent. -

    -
    +

    -s file
    -
    -

    +

    Specifies a prepared dsset file, such as would be generated by dnssec-signzone, to use as a source for the DS RRset instead of querying the parent. -

    -
    +

    -d dig path
    -
    -

    +

    Specifies a path to a dig binary. Used for testing. -

    -
    +

    -D dsfromkey path
    -
    -

    +

    Specifies a path to a dnssec-dsfromkey binary. Used for testing. -

    -
    +

    -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-dsfromkey(8) - , - - dnssec-keygen(8) - , - - dnssec-signzone(8) - , +

    dnssec-dsfromkey(8), + dnssec-keygen(8), + dnssec-signzone(8),

    -
    - +
    @@ -150,6 +107,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-coverage.html b/doc/arm/man.dnssec-coverage.html index 2b28459096f54ac4d5735f68c51a5a093c26bf42..0a52790a9e9df897103c6a732c93c1f402baef07 100644 --- a/doc/arm/man.dnssec-coverage.html +++ b/doc/arm/man.dnssec-coverage.html @@ -10,7 +10,7 @@ dnssec-coverage - + @@ -32,47 +32,22 @@
    - - - - - -
    +

    Name

    -

    - dnssec-coverage - — checks future DNSKEY coverage for a zone -

    +

    dnssec-coverage — checks future DNSKEY coverage for a zone

    - - - -
    +

    Synopsis

    -

    - dnssec-coverage - [-K directory] - [-l length] - [-f file] - [-d DNSKEY TTL] - [-m max TTL] - [-r interval] - [-c compilezone path] - [-k] - [-z] - [zone...] -

    -
    - -
    +

    dnssec-coverage [-K directory] [-l length] [-f file] [-d DNSKEY TTL] [-m max TTL] [-r interval] [-c compilezone path] [-k] [-z] [zone...]

    +
    +

    DESCRIPTION

    - -

    dnssec-coverage +

    dnssec-coverage verifies that the DNSSEC keys for a given zone or a set of zones have timing metadata set properly to ensure no future lapses in DNSSEC coverage.

    -

    +

    If zone is specified, then keys found in the key repository matching that zone are scanned, and an ordered list is generated of the events scheduled for that key (i.e., @@ -85,54 +60,47 @@ key is rolled, and cached data signed by the prior key has not had time to expire from resolver caches.

    -

    +

    If zone is not specified, then all keys in the key repository will be scanned, and all zones for which there are keys will be analyzed. (Note: This method of reporting is only accurate if all the zones that have keys in a given repository share the same TTL parameters.)

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -K directory
    -
    -

    +

    Sets the directory in which keys can be found. Defaults to the current working directory. -

    -
    +

    -f file
    -
    -

    +

    If a file is specified, then the zone is read from that file; the largest TTL and the DNSKEY TTL are determined directly from the zone data, and the -m and -d options do not need to be specified on the command line. -

    -
    +

    -l duration
    -

    +

    The length of time to check for DNSSEC coverage. Key events scheduled further into the future than duration will be ignored, and assumed to be correct.

    -

    +

    The value of duration can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

    -
    +
    -m maximum TTL
    -

    +

    Sets the value to be used as the maximum TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure. When a zone-signing key is @@ -141,26 +109,26 @@ before that key can be purged from the DNSKEY RRset. If that condition does not apply, a warning will be generated.

    -

    +

    The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

    -

    +

    This option is not necessary if the -f has been used to specify a zone file. If -f has been specified, this option may still be used; it will override the value found in the file.

    -

    +

    If this option is not used and the maximum TTL cannot be retrieved from a zone file, a warning is generated and a default value of 1 week is used.

    -
    +
    -d DNSKEY TTL
    -

    +

    Sets the value to be used as the DNSKEY TTL for the zone or zones being analyzed when determining whether there is a possibility of validation failure. When a key is rolled (that @@ -169,12 +137,12 @@ the new key is activated and begins generating signatures. If that condition does not apply, a warning will be generated.

    -

    +

    The length of the TTL can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

    -

    +

    This option is not necessary if -f has been used to specify a zone file from which the TTL of the DNSKEY RRset can be read, or if a default key TTL was @@ -183,15 +151,15 @@ this option may still be used; it will override the values found in the zone file or the key file.

    -

    +

    If this option is not used and the key TTL cannot be retrieved from the zone file or the key file, then a warning is generated and a default value of 1 day is used.

    -
    +
    -r resign interval
    -

    +

    Sets the value to be used as the resign interval for the zone or zones being analyzed when determining whether there is a possibility of validation failure. This value defaults to @@ -201,55 +169,38 @@ named.conf, then it should also be changed here.

    -

    +

    The length of the interval can be set in seconds, or in larger units of time by adding a suffix: 'mi' for minutes, 'h' for hours, 'd' for days, 'w' for weeks, 'mo' for months, 'y' for years.

    -
    +
    -k
    -
    -

    +

    Only check KSK coverage; ignore ZSK events. Cannot be used with -z. -

    -
    +

    -z
    -
    -

    +

    Only check ZSK coverage; ignore KSK events. Cannot be used with -k. -

    -
    +

    -c compilezone path
    -
    -

    +

    Specifies a path to a named-compilezone binary. Used for testing. -

    -
    +

    -
    - -
    +
    +

    SEE ALSO

    - -

    - - dnssec-checkds(8) - , - - dnssec-dsfromkey(8) - , - - dnssec-keygen(8) - , - - dnssec-signzone(8) - +

    + dnssec-checkds(8), + dnssec-dsfromkey(8), + dnssec-keygen(8), + dnssec-signzone(8)

    -
    - +
    @@ -270,6 +221,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-dsfromkey.html b/doc/arm/man.dnssec-dsfromkey.html index b8e2052df5f1348c40b407fc9d7c0b5ecc74cb83..90c2bf9bab26cc1cfa5d643ed3a566f66a963ca2 100644 --- a/doc/arm/man.dnssec-dsfromkey.html +++ b/doc/arm/man.dnssec-dsfromkey.html @@ -10,7 +10,7 @@ dnssec-dsfromkey - + @@ -32,243 +32,159 @@
    - - - - - -
    +

    Name

    -

    - dnssec-dsfromkey - — DNSSEC DS RR generation tool -

    +

    dnssec-dsfromkey — DNSSEC DS RR generation tool

    - - - -
    +

    Synopsis

    -

    - dnssec-dsfromkey - [-v level] - [-1] - [-2] - [-a alg] - [-C] - [-l domain] - [-T TTL] - {keyfile} -

    -

    - dnssec-dsfromkey - {-s} - [-1] - [-2] - [-a alg] - [-K directory] - [-l domain] - [-s] - [-c class] - [-T TTL] - [-f file] - [-A] - [-v level] - {dnsname} -

    -

    - dnssec-dsfromkey - [-h] - [-V] -

    -
    - -
    +

    dnssec-dsfromkey [-v level] [-1] [-2] [-a alg] [-C] [-l domain] [-T TTL] {keyfile}

    +

    dnssec-dsfromkey {-s} [-1] [-2] [-a alg] [-K directory] [-l domain] [-s] [-c class] [-T TTL] [-f file] [-A] [-v level] {dnsname}

    +

    dnssec-dsfromkey [-h] [-V]

    +
    +

    DESCRIPTION

    - -

    dnssec-dsfromkey +

    dnssec-dsfromkey outputs the Delegation Signer (DS) resource record (RR), as defined in RFC 3658 and RFC 4509, for the given key(s).

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -1
    -
    -

    +

    Use SHA-1 as the digest algorithm (the default is to use both SHA-1 and SHA-256). -

    -
    +

    -2
    -
    -

    +

    Use SHA-256 as the digest algorithm. -

    -
    +

    -a algorithm
    -
    -

    +

    Select the digest algorithm. The value of algorithm must be one of SHA-1 (SHA1), SHA-256 (SHA256) or SHA-384 (SHA384). These values are case insensitive. -

    -
    +

    -C
    -
    -

    +

    Generate CDS records rather than DS records. This is mutually exclusive with generating lookaside records. -

    -
    +

    -T TTL
    -
    -

    +

    Specifies the TTL of the DS records. -

    -
    +

    -K directory
    -
    -

    +

    Look for key files (or, in keyset mode, keyset- files) in directory. -

    -
    +

    -f file
    -

    +

    Zone file mode: in place of the keyfile name, the argument is the DNS domain name of a zone master file, which can be read from file. If the zone name is the same as file, then it may be omitted.

    -

    +

    If file is set to "-", then the zone data is read from the standard input. This makes it possible to use the output of the dig command as input, as in:

    -

    +

    dig dnskey example.com | dnssec-dsfromkey -f - example.com

    -
    +
    -A
    -
    -

    +

    Include ZSKs when generating DS records. Without this option, only keys which have the KSK flag set will be converted to DS records and printed. Useful only in zone file mode. -

    -
    +

    -l domain
    -
    -

    +

    Generate a DLV set instead of a DS set. The specified domain is appended to the name for each record in the set. The DNSSEC Lookaside Validation (DLV) RR is described in RFC 4431. This is mutually exclusive with generating CDS records. -

    -
    +

    -s
    -
    -

    +

    Keyset mode: in place of the keyfile name, the argument is the DNS domain name of a keyset file. -

    -
    +

    -c class
    -
    -

    +

    Specifies the DNS class (default is IN). Useful only in keyset or zone file mode. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. -

    -
    +

    -h
    -
    -

    +

    Prints usage information. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -
    - -
    +
    +

    EXAMPLE

    - -

    +

    To build the SHA-256 DS RR from the Kexample.com.+003+26160 keyfile name, the following command would be issued:

    -

    dnssec-dsfromkey -2 Kexample.com.+003+26160 +

    dnssec-dsfromkey -2 Kexample.com.+003+26160

    -

    +

    The command would print something like:

    -

    example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94 +

    example.com. IN DS 26160 5 2 3A1EADA7A74B8D0BA86726B0C227AA85AB8BBD2B2004F41A868A54F0 C5EA0B94

    -
    - -
    +
    +

    FILES

    - -

    +

    The keyfile can be designed by the key identification Knnnn.+aaa+iiiii or the full file name Knnnn.+aaa+iiiii.key as generated by dnssec-keygen(8).

    -

    +

    The keyset file name is built from the directory, the string keyset- and the dnsname.

    -
    - -
    +
    +

    CAVEAT

    - -

    +

    A keyfile error can give a "file not found" even if the file exists.

    -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-keygen(8) - , - - dnssec-signzone(8) - , +

    dnssec-keygen(8), + dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 3658, RFC 4431. RFC 4509.

    -
    - +
    @@ -289,6 +205,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-importkey.html b/doc/arm/man.dnssec-importkey.html index 30b483db40abff45d6a7fe092e95b16bd10ed5a7..2e1588412d25536bba5c0f8eeb3ba28fb063e7f2 100644 --- a/doc/arm/man.dnssec-importkey.html +++ b/doc/arm/man.dnssec-importkey.html @@ -10,7 +10,7 @@ dnssec-importkey - + @@ -32,56 +32,18 @@
    - - - - - -
    +

    Name

    -

    - dnssec-importkey - — import DNSKEY records from external systems so they can be managed -

    +

    dnssec-importkey — import DNSKEY records from external systems so they can be managed

    - - - -
    +

    Synopsis

    -

    - dnssec-importkey - [-K directory] - [-L ttl] - [-P date/offset] - [-P sync date/offset] - [-D date/offset] - [-D sync date/offset] - [-h] - [-v level] - [-V] - {keyfile} -

    -

    - dnssec-importkey - {-f filename} - [-K directory] - [-L ttl] - [-P date/offset] - [-P sync date/offset] - [-D date/offset] - [-D sync date/offset] - [-h] - [-v level] - [-V] - [dnsname] -

    -
    - -
    +

    dnssec-importkey [-K directory] [-L ttl] [-P date/offset] [-P sync date/offset] [-D date/offset] [-D sync date/offset] [-h] [-v level] [-V] {keyfile}

    +

    dnssec-importkey {-f filename} [-K directory] [-L ttl] [-P date/offset] [-P sync date/offset] [-D date/offset] [-D sync date/offset] [-h] [-v level] [-V] [dnsname]

    +
    +

    DESCRIPTION

    - -

    dnssec-importkey +

    dnssec-importkey reads a public DNSKEY record and generates a pair of .key/.private files. The DNSKEY record may be read from an existing .key file, in which case a corresponding .private file @@ -89,7 +51,7 @@ from the standard input, in which case both .key and .private files will be generated.

    -

    +

    The newly-created .private file does not contain private key data, and cannot be used for signing. However, having a .private file makes it possible to set @@ -98,68 +60,53 @@ public key can be added to and removed from the DNSKEY RRset on schedule even if the true private key is stored offline.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -f filename
    -

    +

    Zone file mode: instead of a public keyfile name, the argument is the DNS domain name of a zone master file, which can be read from file. If the domain name is the same as file, then it may be omitted.

    -

    +

    If file is set to "-", then the zone data is read from the standard input.

    -
    +
    -K directory
    -
    -

    +

    Sets the directory in which the key files are to reside. -

    -
    +

    -L ttl
    -
    -

    +

    Sets the default TTL to use for this key when it is converted into a DNSKEY RR. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence. Setting the default TTL to 0 or none removes it. -

    -
    +

    -h
    -
    -

    +

    Emit usage message and exit. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -
    - -
    +
    +

    TIMING OPTIONS

    - -

    +

    Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as an offset from the present time. For convenience, if such an offset @@ -170,66 +117,48 @@ is computed in seconds. To explicitly prevent a date from being set, use 'none' or 'never'.

    - -
    +
    -P date/offset
    -
    -

    +

    Sets the date on which a key is to be published to the zone. After that date, the key will be included in the zone but will not be used to sign it. -

    -
    +

    -P sync date/offset
    -
    -

    +

    Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone. -

    -
    +

    -D date/offset
    -
    -

    +

    Sets the date on which the key is to be deleted. After that date, the key will no longer be included in the zone. (It may remain in the key repository, however.) -

    -
    +

    -D sync date/offset
    -
    -

    +

    Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted. -

    -
    +

    -
    - -
    +
    +

    FILES

    - -

    +

    A keyfile can be designed by the key identification Knnnn.+aaa+iiiii or the full file name Knnnn.+aaa+iiiii.key as generated by dnssec-keygen(8).

    -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-keygen(8) - , - - dnssec-signzone(8) - , +

    dnssec-keygen(8), + dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 5011.

    -
    - +
    @@ -250,6 +179,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-keyfromlabel.html b/doc/arm/man.dnssec-keyfromlabel.html index 6a8f47ebb8943988001a2cbe7cf10d0ef8ae4978..b89f0efa6b5af4f0967575a05f738b8c5629bbae 100644 --- a/doc/arm/man.dnssec-keyfromlabel.html +++ b/doc/arm/man.dnssec-keyfromlabel.html @@ -10,7 +10,7 @@ dnssec-keyfromlabel - + @@ -32,58 +32,17 @@
    - - - - - -
    +

    Name

    -

    - dnssec-keyfromlabel - — DNSSEC key generation tool -

    +

    dnssec-keyfromlabel — DNSSEC key generation tool

    - - - -
    +

    Synopsis

    -

    - dnssec-keyfromlabel - {-l label} - [-3] - [-a algorithm] - [-A date/offset] - [-c class] - [-D date/offset] - [-D sync date/offset] - [-E engine] - [-f flag] - [-G] - [-I date/offset] - [-i interval] - [-k] - [-K directory] - [-L ttl] - [-n nametype] - [-P date/offset] - [-P sync date/offset] - [-p protocol] - [-R date/offset] - [-S key] - [-t type] - [-v level] - [-V] - [-y] - {name} -

    -
    - -
    +

    dnssec-keyfromlabel {-l label} [-3] [-a algorithm] [-A date/offset] [-c class] [-D date/offset] [-D sync date/offset] [-E engine] [-f flag] [-G] [-I date/offset] [-i interval] [-k] [-K directory] [-L ttl] [-n nametype] [-P date/offset] [-P sync date/offset] [-p protocol] [-R date/offset] [-S key] [-t type] [-v level] [-V] [-y] {name}

    +
    +

    DESCRIPTION

    - -

    dnssec-keyfromlabel +

    dnssec-keyfromlabel generates a key pair of files that referencing a key object stored in a cryptographic hardware service module (HSM). The private key file can be used for DNSSEC signing of zone data as if it were a @@ -91,63 +50,58 @@ but the key material is stored within the HSM, and the actual signing takes place there.

    -

    +

    The name of the key is specified on the command line. This must match the name of the zone for which the key is being generated.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -a algorithm
    -

    +

    Selects the cryptographic algorithm. The value of algorithm must be one of RSAMD5, RSASHA1, DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, ECDSAP256SHA256, ECDSAP384SHA384, ED25519 or ED448.

    -

    +

    If no algorithm is specified, then RSASHA1 will be used by default, unless the -3 option is specified, in which case NSEC3RSASHA1 will be used instead. (If -3 is used and an algorithm is specified, that algorithm will be checked for compatibility with NSEC3.)

    -

    +

    These values are case insensitive. In some cases, abbreviations are supported, such as ECDSA256 for ECDSAP256SHA256 and ECDSA384 for ECDSAP384SHA384. If RSASHA1 or DSA is specified along with the -3 option, then NSEC3RSASHA1 or NSEC3DSA will be used instead.

    -

    +

    As of BIND 9.12.0, this option is mandatory except when using the -S option (which copies the algorithm from the predecessory key). Previously, the default for newly generated keys was RSASHA1.

    -
    +
    -3
    -
    -

    +

    Use an NSEC3-capable algorithm to generate a DNSSEC key. If this option is used with an algorithm that has both NSEC and NSEC3 versions, then the NSEC3 version will be used; for example, dnssec-keygen -3a RSASHA1 specifies the NSEC3RSASHA1 algorithm. -

    -
    +

    -E engine
    -

    +

    Specifies the cryptographic hardware to use.

    -

    +

    When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service @@ -155,20 +109,20 @@ (--enable-native-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "--with-pkcs11".

    -
    +
    -l label
    -

    +

    Specifies the label for a key pair in the crypto hardware.

    -

    +

    When BIND 9 is built with OpenSSL-based PKCS#11 support, the label is an arbitrary string that identifies a particular key. It may be preceded by an optional OpenSSL engine name, followed by a colon, as in "pkcs11:keylabel".

    -

    +

    When BIND 9 is built with native PKCS#11 support, the label is a PKCS#11 URI string in the format "pkcs11:keyword=value[;keyword=value;...]" @@ -177,7 +131,7 @@ which the HSM's PIN code can be obtained. The label will be stored in the on-disk "private" file.

    -

    +

    If the label contains a pin-source field, tools using the generated key files will be able to use the HSM for signing and other @@ -186,21 +140,18 @@ may reduce the security advantage of using an HSM; be sure this is what you want to do before making use of this feature.

    -
    +
    -n nametype
    -
    -

    +

    Specifies the owner type of the key. The value of nametype must either be ZONE (for a DNSSEC zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with a host (KEY)), USER (for a key associated with a user(KEY)) or OTHER (DNSKEY). These values are case insensitive. -

    -
    +

    -C
    -
    -

    +

    Compatibility mode: generates an old-style key, without any metadata. By default, dnssec-keyfromlabel will include the key's creation date in the metadata stored @@ -208,71 +159,53 @@ (publication date, activation date, etc). Keys that include this data may be incompatible with older versions of BIND; the -C option suppresses them. -

    -
    +

    -c class
    -
    -

    +

    Indicates that the DNS record containing the key should have the specified class. If not specified, class IN is used. -

    -
    +

    -f flag
    -
    -

    +

    Set the specified flag in the flag field of the KEY/DNSKEY record. The only recognized flags are KSK (Key Signing Key) and REVOKE. -

    -
    +

    -G
    -
    -

    +

    Generate a key, but do not publish it or sign with it. This option is incompatible with -P and -A. -

    -
    +

    -h
    -
    -

    +

    Prints a short summary of the options and arguments to dnssec-keyfromlabel. -

    -
    +

    -K directory
    -
    -

    +

    Sets the directory in which the key files are to be written. -

    -
    +

    -k
    -
    -

    +

    Generate KEY records rather than DNSKEY records. -

    -
    +

    -L ttl
    -
    -

    +

    Sets the default TTL to use for this key when it is converted into a DNSKEY RR. If the key is imported into a zone, this is the TTL that will be used for it, unless there was already a DNSKEY RRset in place, in which case the existing TTL would take precedence. Setting the default TTL to 0 or none removes it. -

    -
    +

    -p protocol
    -
    -

    +

    Sets the protocol value for the key. The protocol is a number between 0 and 255. The default is 3 (DNSSEC). Other possible values for this argument are listed in RFC 2535 and its successors. -

    -
    +

    -S key
    -
    -

    +

    Generate a key as an explicit successor to an existing key. The name, algorithm, size, and type of the key will be set to match the predecessor. The activation date of the new @@ -280,47 +213,35 @@ one. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days. -

    -
    +

    -t type
    -
    -

    +

    Indicates the use of the key. type must be one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default is AUTHCONF. AUTH refers to the ability to authenticate data, and CONF the ability to encrypt data. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -y
    -
    -

    +

    Allows DNSSEC key files to be generated even if the key ID would collide with that of an existing key, in the event of either key being revoked. (This is only safe to use if you are sure you won't be using RFC 5011 trust anchor maintenance with either of the keys involved.) -

    -
    +

    -
    - -
    +
    +

    TIMING OPTIONS

    - - -

    +

    Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as an offset from the present time. For convenience, if such an offset @@ -331,67 +252,52 @@ is computed in seconds. To explicitly prevent a date from being set, use 'none' or 'never'.

    - -
    +
    -P date/offset
    -
    -

    +

    Sets the date on which a key is to be published to the zone. After that date, the key will be included in the zone but will not be used to sign it. If not set, and if the -G option has not been used, the default is "now". -

    -
    +

    -P sync date/offset
    -
    -

    +

    Sets the date on which the CDS and CDNSKEY records which match this key are to be published to the zone. -

    -
    +

    -A date/offset
    -
    -

    +

    Sets the date on which the key is to be activated. After that date, the key will be included in the zone and used to sign it. If not set, and if the -G option has not been used, the default is "now". -

    -
    +

    -R date/offset
    -
    -

    +

    Sets the date on which the key is to be revoked. After that date, the key will be flagged as revoked. It will be included in the zone and will be used to sign it. -

    -
    +

    -I date/offset
    -
    -

    +

    Sets the date on which the key is to be retired. After that date, the key will still be included in the zone, but it will not be used to sign it. -

    -
    +

    -D date/offset
    -
    -

    +

    Sets the date on which the key is to be deleted. After that date, the key will no longer be included in the zone. (It may remain in the key repository, however.) -

    -
    +

    -D sync date/offset
    -
    -

    +

    Sets the date on which the CDS and CDNSKEY records which match this key are to be deleted. -

    -
    +

    -i interval
    -

    +

    Sets the prepublication interval for a key. If set, then the publication and activation dates must be separated by at least this much time. If the activation date is specified but the @@ -400,84 +306,69 @@ the publication date is specified but activation date isn't, then activation will be set to this much time after publication.

    -

    +

    If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero.

    -

    +

    As with date offsets, if the argument is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the interval is measured in years, months, weeks, days, hours, or minutes, respectively. Without a suffix, the interval is measured in seconds.

    -
    +
    -
    - -
    +
    +

    GENERATED KEY FILES

    - -

    +

    When dnssec-keyfromlabel completes successfully, it prints a string of the form Knnnn.+aaa+iiiii to the standard output. This is an identification string for the key files it has generated.

    -
      -
    • -

      nnnn is the key name. -

      -
      • -
    • -

      aaa is the numeric representation +

        +

      • nnnn is the key name. +

        • +

      • aaa is the numeric representation of the algorithm. -

        -
        • -
      • -

        iiiii is the key identifier (or +

        • +

      • iiiii is the key identifier (or footprint). -

        -
        • +

      -

      dnssec-keyfromlabel +

      dnssec-keyfromlabel creates two files, with names based on the printed string. Knnnn.+aaa+iiiii.key contains the public key, and Knnnn.+aaa+iiiii.private contains the private key.

      -

      +

      The .key file contains a DNS KEY record that can be inserted into a zone file (directly or with a $INCLUDE statement).

      -

      +

      The .private file contains algorithm-specific fields. For obvious security reasons, this file does not have general read permission.

      -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-keygen(8) - , - - dnssec-signzone(8) - , +

    dnssec-keygen(8), + dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 4034, The PKCS#11 URI Scheme (draft-pechanec-pkcs11uri-13).

    -
    - +
    @@ -498,6 +389,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-keygen.html b/doc/arm/man.dnssec-keygen.html index 278c364becc235f5dd2c7c72c229aa6d6270493f..c7a5461a687217d40ff3baaa2bb5e8cd4b304bde 100644 --- a/doc/arm/man.dnssec-keygen.html +++ b/doc/arm/man.dnssec-keygen.html @@ -10,7 +10,7 @@ dnssec-keygen - + @@ -32,90 +32,41 @@
    - - - - - -
    +

    Name

    -

    - dnssec-keygen - — DNSSEC key generation tool -

    +

    dnssec-keygen — DNSSEC key generation tool

    - - - -
    +

    Synopsis

    -

    - dnssec-keygen - [-a algorithm] - [-b keysize] - [-n nametype] - [-3] - [-A date/offset] - [-C] - [-c class] - [-D date/offset] - [-D sync date/offset] - [-E engine] - [-f flag] - [-G] - [-g generator] - [-h] - [-I date/offset] - [-i interval] - [-K directory] - [-k] - [-L ttl] - [-P date/offset] - [-P sync date/offset] - [-p protocol] - [-q] - [-R date/offset] - [-S key] - [-s strength] - [-t type] - [-V] - [-v level] - [-z] - {name} -

    -
    - -
    +

    dnssec-keygen [-a algorithm] [-b keysize] [-n nametype] [-3] [-A date/offset] [-C] [-c class] [-D date/offset] [-D sync date/offset] [-E engine] [-f flag] [-G] [-g generator] [-h] [-I date/offset] [-i interval] [-K directory] [-k] [-L ttl] [-P date/offset] [-P sync date/offset] [-p protocol] [-q] [-R date/offset] [-S key] [-s strength] [-t type] [-V] [-v level] [-z] {name}

    +
    +

    DESCRIPTION

    - -

    dnssec-keygen +

    dnssec-keygen generates keys for DNSSEC (Secure DNS), as defined in RFC 2535 and RFC 4034. It can also generate keys for use with TSIG (Transaction Signatures) as defined in RFC 2845, or TKEY (Transaction Key) as defined in RFC 2930.

    -

    +

    The name of the key is specified on the command line. For DNSSEC keys, this must match the name of the zone for which the key is being generated.

    -

    +

    The dnssec-keymgr command acts as a wrapper around dnssec-keygen, generating and updating keys as needed to enforce defined security policies such as key rollover scheduling. Using dnssec-keymgr may be preferable to direct use of dnssec-keygen.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -a algorithm
    -

    +

    Selects the cryptographic algorithm. For DNSSEC keys, the value of algorithm must be one of RSAMD5, RSASHA1, DSA, NSEC3RSASHA1, NSEC3DSA, RSASHA256, RSASHA512, @@ -124,28 +75,28 @@ his value will automatically set the -T KEY option as well.

    -

    +

    These values are case insensitive. In some cases, abbreviations are supported, such as ECDSA256 for ECDSAP256SHA256 and ECDSA384 for ECDSAP384SHA384. If RSASHA1 or DSA is specified along with the -3 option, then NSEC3RSASHA1 or NSEC3DSA will be used instead.

    -

    +

    This parameter must be specified except when using the -S option, which copies the algorithm from the predecessor key.

    -

    +

    In prior releases, HMAC algorithms could be generated for use as TSIG keys, but that feature has been removed as of BIND 9.13.0. Use tsig-keygen to generate TSIG keys.

    -
    +
    -b keysize
    -

    +

    Specifies the number of bits in the key. The choice of key size depends on the algorithm used. RSA keys must be between 1024 and 2048 bits. Diffie Hellman keys must be between @@ -154,38 +105,33 @@ between 1 and 512 bits. Elliptic curve algorithms don't need this parameter.

    -

    +

    If the key size is not specified, some algorithms have pre-defined defaults. For example, RSA keys for use as DNSSEC zone signing keys have a default size of 1024 bits; RSA keys for use as key signing keys (KSKs, generated with -f KSK) default to 2048 bits.

    -
    +
    -n nametype
    -
    -

    +

    Specifies the owner type of the key. The value of nametype must either be ZONE (for a DNSSEC zone key (KEY/DNSKEY)), HOST or ENTITY (for a key associated with a host (KEY)), USER (for a key associated with a user(KEY)) or OTHER (DNSKEY). These values are case insensitive. Defaults to ZONE for DNSKEY generation. -

    -
    +

    -3
    -
    -

    +

    Use an NSEC3-capable algorithm to generate a DNSSEC key. If this option is used with an algorithm that has both NSEC and NSEC3 versions, then the NSEC3 version will be used; for example, dnssec-keygen -3a RSASHA1 specifies the NSEC3RSASHA1 algorithm. -

    -
    +

    -C
    -
    -

    +

    Compatibility mode: generates an old-style key, without any metadata. By default, dnssec-keygen will include the key's creation date in the metadata stored @@ -193,21 +139,18 @@ (publication date, activation date, etc). Keys that include this data may be incompatible with older versions of BIND; the -C option suppresses them. -

    -
    +

    -c class
    -
    -

    +

    Indicates that the DNS record containing the key should have the specified class. If not specified, class IN is used. -

    -
    +

    -E engine
    -

    +

    Specifies the cryptographic hardware to use, when applicable.

    -

    +

    When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service @@ -215,52 +158,39 @@ (--enable-native-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "--with-pkcs11".

    -
    +
    -f flag
    -
    -

    +

    Set the specified flag in the flag field of the KEY/DNSKEY record. The only recognized flags are KSK (Key Signing Key) and REVOKE. -

    -
    +

    -G
    -
    -

    +

    Generate a key, but do not publish it or sign with it. This option is incompatible with -P and -A. -

    -
    +

    -g generator
    -
    -

    +

    If generating a Diffie Hellman key, use this generator. Allowed values are 2 and 5. If no generator is specified, a known prime from RFC 2539 will be used if possible; otherwise the default is 2. -

    -
    +

    -h
    -
    -

    +

    Prints a short summary of the options and arguments to dnssec-keygen. -

    -
    +

    -K directory
    -
    -

    +

    Sets the directory in which the key files are to be written. -

    -
    +

    -k
    -
    -

    +

    Deprecated in favor of -T KEY. -

    -
    +

    -L ttl
    -
    -

    +

    Sets the default TTL to use for this key when it is converted into a DNSKEY RR. If the key is imported into a zone, this is the TTL that will be used for it, unless there was @@ -269,20 +199,16 @@ is no existing DNSKEY RRset, the TTL will default to the SOA TTL. Setting the default TTL to 0 or none is the same as leaving it unset. -

    -
    +

    -p protocol
    -
    -

    +

    Sets the protocol value for the generated key. The protocol is a number between 0 and 255. The default is 3 (DNSSEC). Other possible values for this argument are listed in RFC 2535 and its successors. -

    -
    +

    -q
    -
    -

    +

    Quiet mode: Suppresses unnecessary output, including progress indication. Without this option, when dnssec-keygen is run interactively @@ -294,11 +220,9 @@ round of the Miller-Rabin primality test; a space means that the number has passed all the tests and is a satisfactory key. -

    -
    +

    -S key
    -
    -

    +

    Create a new key which is an explicit successor to an existing key. The name, algorithm, size, and type of the key will be set to match the existing key. The activation @@ -306,19 +230,16 @@ the existing one. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days. -

    -
    +

    -s strength
    -
    -

    +

    Specifies the strength value of the key. The strength is a number between 0 and 15, and currently has no defined purpose in DNSSEC. -

    -
    +

    -T rrtype
    -

    +

    Specifies the resource record type to use for the key. rrtype must be either DNSKEY or KEY. The default is DNSKEY when using a DNSSEC algorithm, but it can be @@ -330,36 +251,27 @@ Specifying any TSIG algorithm (HMAC-* or DH) with -a forces this option to KEY.

    -
    +
    -t type
    -
    -

    +

    Indicates the use of the key. type must be one of AUTHCONF, NOAUTHCONF, NOAUTH, or NOCONF. The default is AUTHCONF. AUTH refers to the ability to authenticate data, and CONF the ability to encrypt data. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -
    - -
    +
    +

    TIMING OPTIONS

    - - -

    +

    Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as an offset from the present time. For convenience, if such an offset @@ -370,69 +282,54 @@ is computed in seconds. To explicitly prevent a date from being set, use 'none' or 'never'.

    - -
    +
    -P date/offset
    -
    -

    +

    Sets the date on which a key is to be published to the zone. After that date, the key will be included in the zone but will not be used to sign it. If not set, and if the -G option has not been used, the default is "now". -

    -
    +

    -P sync date/offset
    -
    -

    +

    Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone. -

    -
    +

    -A date/offset
    -
    -

    +

    Sets the date on which the key is to be activated. After that date, the key will be included in the zone and used to sign it. If not set, and if the -G option has not been used, the default is "now". If set, if and -P is not set, then the publication date will be set to the activation date minus the prepublication interval. -

    -
    +

    -R date/offset
    -
    -

    +

    Sets the date on which the key is to be revoked. After that date, the key will be flagged as revoked. It will be included in the zone and will be used to sign it. -

    -
    +

    -I date/offset
    -
    -

    +

    Sets the date on which the key is to be retired. After that date, the key will still be included in the zone, but it will not be used to sign it. -

    -
    +

    -D date/offset
    -
    -

    +

    Sets the date on which the key is to be deleted. After that date, the key will no longer be included in the zone. (It may remain in the key repository, however.) -

    -
    +

    -D sync date/offset
    -
    -

    +

    Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted. -

    -
    +

    -i interval
    -

    +

    Sets the prepublication interval for a key. If set, then the publication and activation dates must be separated by at least this much time. If the activation date is specified but the @@ -441,51 +338,42 @@ the publication date is specified but activation date isn't, then activation will be set to this much time after publication.

    -

    +

    If the key is being created as an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero.

    -

    +

    As with date offsets, if the argument is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the interval is measured in years, months, weeks, days, hours, or minutes, respectively. Without a suffix, the interval is measured in seconds.

    -
    +
    -
    - - -
    +
    +

    GENERATED KEYS

    - -

    +

    When dnssec-keygen completes successfully, it prints a string of the form Knnnn.+aaa+iiiii to the standard output. This is an identification string for the key it has generated.

    -
      -
    • -

      nnnn is the key name. -

      -
      • -
    • -

      aaa is the numeric representation +

        +

      • nnnn is the key name. +

        • +

      • aaa is the numeric representation of the algorithm. -

        -
        • -
      • -

        iiiii is the key identifier (or +

        • +

      • iiiii is the key identifier (or footprint). -

        -
        • +

      -

      dnssec-keygen +

      dnssec-keygen creates two files, with names based on the printed string. Knnnn.+aaa+iiiii.key contains the public key, and @@ -493,61 +381,54 @@ private key.

      -

      +

      The .key file contains a DNS KEY record that can be inserted into a zone file (directly or with a $INCLUDE statement).

      -

      +

      The .private file contains algorithm-specific fields. For obvious security reasons, this file does not have general read permission.

      -

      +

      Both .key and .private files are generated for symmetric cryptography algorithms such as HMAC-MD5, even though the public and private key are equivalent.

      -
    - -
    +
    +

    EXAMPLE

    - -

    +

    To generate a 768-bit DSA key for the domain example.com, the following command would be issued:

    -

    dnssec-keygen -a DSA -b 768 -n ZONE example.com +

    dnssec-keygen -a DSA -b 768 -n ZONE example.com

    -

    +

    The command would print a string of the form:

    -

    Kexample.com.+003+26160 +

    Kexample.com.+003+26160

    -

    +

    In this example, dnssec-keygen creates the files Kexample.com.+003+26160.key and Kexample.com.+003+26160.private.

    -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-signzone(8) - , +

    dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 2539, RFC 2845, RFC 4034.

    -
    - +
    @@ -568,6 +449,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-keymgr.html b/doc/arm/man.dnssec-keymgr.html index aaad294748e33569445a996a44cae3fb967b2c2e..e03561cb8095e9d275c46fa3e9a3c6ba5e24929b 100644 --- a/doc/arm/man.dnssec-keymgr.html +++ b/doc/arm/man.dnssec-keymgr.html @@ -10,7 +10,7 @@ dnssec-keymgr - + @@ -32,48 +32,24 @@
    - - - - - -
    +

    Name

    -

    - dnssec-keymgr - — Ensures correct DNSKEY coverage for a zone based on a defined policy -

    +

    dnssec-keymgr — Ensures correct DNSKEY coverage for a zone based on a defined policy

    - - - -
    +

    Synopsis

    -

    - dnssec-keymgr - [-K directory] - [-c file] - [-f] - [-k] - [-q] - [-v] - [-z] - [-g path] - [-s path] - [zone...] -

    -
    - -
    +

    dnssec-keymgr [-K directory] [-c file] [-f] [-k] [-q] [-v] [-z] [-g path] [-s path] [zone...]

    +
    +

    DESCRIPTION

    -

    +

    dnssec-keymgr is a high level Python wrapper to facilitate the key rollover process for zones handled by BIND. It uses the BIND commands for manipulating DNSSEC key metadata: dnssec-keygen and dnssec-settime.

    -

    +

    DNSSEC policy can be read from a configuration file (default /etc/dnssec-policy.conf), from which the key parameters, publication and rollover schedule, and desired @@ -81,14 +57,14 @@ file may be used to define individual DNSSEC policies on a per-zone basis, or to set a default policy used for all zones.

    -

    +

    When dnssec-keymgr runs, it examines the DNSSEC keys for one or more zones, comparing their timing metadata against the policies for those zones. If key settings do not conform to the DNSSEC policy (for example, because the policy has been changed), they are automatically corrected.

    -

    +

    A zone policy can specify a duration for which we want to ensure the key correctness (coverage). It can also specify a rollover period (roll-period). @@ -96,41 +72,37 @@ coverage period ends, then a successor key will automatically be created and added to the end of the key series.

    -

    +

    If zones are specified on the command line, dnssec-keymgr will examine only those zones. If a specified zone does not already have keys in place, then keys will be generated for it according to policy.

    -

    +

    If zones are not specified on the command line, then dnssec-keymgr will search the key directory (either the current working directory or the directory set by the -K option), and check the keys for all the zones represented in the directory.

    -

    +

    It is expected that this tool will be run automatically and unattended (for example, by cron).

    -
    - -
    +
    +

    OPTIONS

    -
    +
    -c file
    -
    -

    +

    If -c is specified, then the DNSSEC policy is read from file. (If not specified, then the policy is read from /etc/dnssec-policy.conf; if that file doesn't exist, a built-in global default policy is used.) -

    -
    +

    -f
    -
    -

    +

    Force: allow updating of key events even if they are already in the past. This is not recommended for use with zones in which keys have already been published. However, @@ -139,77 +111,58 @@ keys have not been published in a zone as yet, then this option can be used to clean them up and turn them into a proper series of keys with appropriate rollover intervals. -

    -
    +

    -g keygen-path
    -
    -

    +

    Specifies a path to a dnssec-keygen binary. Used for testing. See also the -s option. -

    -
    +

    -h
    -
    -

    +

    Print the dnssec-keymgr help summary and exit. -

    -
    +

    -K directory
    -
    -

    +

    Sets the directory in which keys can be found. Defaults to the current working directory. -

    -
    +

    -k
    -
    -

    +

    Only apply policies to KSK keys. See also the -z option. -

    -
    +

    -q
    -
    -

    +

    Quiet: suppress printing of dnssec-keygen and dnssec-settime. -

    -
    +

    -s settime-path
    -
    -

    +

    Specifies a path to a dnssec-settime binary. Used for testing. See also the -g option. -

    -
    +

    -v
    -
    -

    +

    Print the dnssec-keymgr version and exit. -

    -
    +

    -z
    -
    -

    +

    Only apply policies to ZSK keys. See also the -k option. -

    -
    +

    -
    - -
    +
    +

    POLICY CONFIGURATION

    -

    +

    The dnssec-policy.conf file can specify three kinds of policies:

    -
      -
    • -

      +

        +

      • Policy classes (policy name { ... };) can be inherited by zone policies or other policy classes; these @@ -218,42 +171,34 @@ 1024-bit key sizes, but a class extra might specify 2048 bits instead; extra would be used for zones that had unusually high security needs. -

        -
        • -
      • -

        +

        • +

      • Algorithm policies: (algorithm-policy algorithm { ... }; ) override default per-algorithm settings. For example, by default, RSASHA256 keys use 2048-bit key sizes for both KSK and ZSK. This can be modified using algorithm-policy, and the new key sizes would then be used for any key of type RSASHA256. -

        -
        • -
      • -

        +

        • +

      • Zone policies: (zone name { ... }; ) set policy for a single zone by name. A zone policy can inherit a policy class by including a policy option. Zone names beginning with digits (i.e., 0-9) must be quoted. -

        -
        • +

      -

      +

      Options that can be specified in policies:

      -
      +
      algorithm
      -
      -

      +

      The key algorithm. If no policy is defined, the default is RSASHA256. -

      -
      +

      coverage
      -
      -

      +

      The length of time to ensure that keys will be correct; no action will be taken to create new keys to be activated after this time. This can be represented as a number of seconds, or as a duration using @@ -261,113 +206,83 @@ A default value for this option can be set in algorithm policies as well as in policy classes or zone policies. If no policy is configured, the default is six months. -

      -
      +

      directory
      -
      -

      +

      Specifies the directory in which keys should be stored. -

      -
      +

      key-size
      -
      -

      +

      Specifies the number of bits to use in creating keys. Takes two arguments: keytype (eihter "zsk" or "ksk") and size. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies. If no policy is configured, the default is 1024 bits for DSA keys and 2048 for RSA. -

      -
      +

      keyttl
      -
      -

      +

      The key TTL. If no policy is defined, the default is one hour. -

      -
      +

      post-publish
      -
      -

      +

      How long after inactivation a key should be deleted from the zone. Note: If roll-period is not set, this value is ignored. Takes two arguments: keytype (eihter "zsk" or "ksk") and a duration. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies. The default is one month. -

      -
      +

      pre-publish
      -
      -

      +

      How long before activation a key should be published. Note: If roll-period is not set, this value is ignored. Takes two arguments: keytype (either "zsk" or "ksk") and a duration. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies. The default is one month. -

      -
      +

      roll-period
      -
      -

      +

      How frequently keys should be rolled over. Takes two arguments: keytype (eihter "zsk" or "ksk") and a duration. A default value for this option can be set in algorithm policies as well as in policy classes or zone policies. If no policy is configured, the default is one year for ZSK's. KSK's do not roll over by default. -

      -
      +

      standby
      -
      -

      +

      Not yet implemented. -

      -
      +

      -
      - -
      +
      +

      REMAINING WORK

      -
        -
      • -

        +

          +

        • Enable scheduling of KSK rollovers using the -P sync and -D sync options to dnssec-keygen and dnssec-settime. Check the parent zone (as in dnssec-checkds) to determine when it's safe for the key to roll. -

          -
          • -
        • -

          +

          • +

        • Allow configuration of standby keys and use of the REVOKE bit, for keys that use RFC 5011 semantics. -

          -
          • +

        -
      - -
      +
      +

      SEE ALSO

      -

      - - dnssec-coverage(8) - , - - dnssec-keygen(8) - , - - dnssec-settime(8) - , - - dnssec-checkds(8) - +

      + dnssec-coverage(8), + dnssec-keygen(8), + dnssec-settime(8), + dnssec-checkds(8)

      -
      - +
    @@ -388,6 +303,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-revoke.html b/doc/arm/man.dnssec-revoke.html index 4671a24372a6c1dd7c9bc7b6c64c7baf47e00198..1bd7ed87ec60e4a192149f677a3dec47c13416f4 100644 --- a/doc/arm/man.dnssec-revoke.html +++ b/doc/arm/man.dnssec-revoke.html @@ -10,7 +10,7 @@ dnssec-revoke - + @@ -32,88 +32,52 @@
    - - - - - -
    +

    Name

    -

    - dnssec-revoke - — set the REVOKED bit on a DNSSEC key -

    +

    dnssec-revoke — set the REVOKED bit on a DNSSEC key

    - - - -
    +

    Synopsis

    -

    - dnssec-revoke - [-hr] - [-v level] - [-V] - [-K directory] - [-E engine] - [-f] - [-R] - {keyfile} -

    -
    - -
    +

    dnssec-revoke [-hr] [-v level] [-V] [-K directory] [-E engine] [-f] [-R] {keyfile}

    +
    +

    DESCRIPTION

    - -

    dnssec-revoke +

    dnssec-revoke reads a DNSSEC key file, sets the REVOKED bit on the key as defined in RFC 5011, and creates a new pair of key files containing the now-revoked key.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -h
    -
    -

    +

    Emit usage message and exit. -

    -
    +

    -K directory
    -
    -

    +

    Sets the directory in which the key files are to reside. -

    -
    +

    -r
    -
    -

    +

    After writing the new keyset files remove the original keyset files. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -E engine
    -

    +

    Specifies the cryptographic hardware to use, when applicable.

    -

    +

    When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service @@ -121,36 +85,27 @@ (--enable-native-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "--with-pkcs11".

    -
    +
    -f
    -
    -

    +

    Force overwrite: Causes dnssec-revoke to write the new key pair even if a file already exists matching the algorithm and key ID of the revoked key. -

    -
    +

    -R
    -
    -

    +

    Print the key tag of the key with the REVOKE bit set but do not revoke the key. -

    -
    +

    -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-keygen(8) - , +

    dnssec-keygen(8), BIND 9 Administrator Reference Manual, RFC 5011.

    -
    - +
    @@ -171,6 +126,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-settime.html b/doc/arm/man.dnssec-settime.html index 030bb0d157c26b817905d18665772b8f4a028bef..187a178bff1241d3fa0243fa5746ead07c125aab 100644 --- a/doc/arm/man.dnssec-settime.html +++ b/doc/arm/man.dnssec-settime.html @@ -10,7 +10,7 @@ dnssec-settime - + @@ -32,49 +32,17 @@
    - - - - - -
    +

    Name

    -

    - dnssec-settime - — set the key timing metadata for a DNSSEC key -

    +

    dnssec-settime — set the key timing metadata for a DNSSEC key

    - - - -
    +

    Synopsis

    -

    - dnssec-settime - [-f] - [-K directory] - [-L ttl] - [-P date/offset] - [-P sync date/offset] - [-A date/offset] - [-R date/offset] - [-I date/offset] - [-D date/offset] - [-D sync date/offset] - [-S key] - [-i interval] - [-h] - [-V] - [-v level] - [-E engine] - {keyfile} -

    -
    - -
    +

    dnssec-settime [-f] [-K directory] [-L ttl] [-P date/offset] [-P sync date/offset] [-A date/offset] [-R date/offset] [-I date/offset] [-D date/offset] [-D sync date/offset] [-S key] [-i interval] [-h] [-V] [-v level] [-E engine] {keyfile}

    +
    +

    DESCRIPTION

    - -

    dnssec-settime +

    dnssec-settime reads a DNSSEC private key file and sets the key timing metadata as specified by the -P, -A, -R, -I, and -D @@ -83,12 +51,12 @@ determine when a key is to be published, whether it should be used for signing a zone, etc.

    -

    +

    If none of these options is set on the command line, then dnssec-settime simply prints the key timing metadata already stored in the key.

    -

    +

    When key metadata fields are changed, both files of a key pair (Knnnn.+aaa+iiiii.key and Knnnn.+aaa+iiiii.private) are regenerated. @@ -97,16 +65,12 @@ file. The private file's permissions are always set to be inaccessible to anyone other than the owner (mode 0600).

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -f
    -
    -

    +

    Force an update of an old-format key with no metadata fields. Without this option, dnssec-settime will fail when attempting to update a legacy key. With this option, @@ -115,17 +79,13 @@ set to the present time. If no other values are specified, then the key's publication and activation dates will also be set to the present time. -

    -
    +

    -K directory
    -
    -

    +

    Sets the directory in which the key files are to reside. -

    -
    +

    -L ttl
    -
    -

    +

    Sets the default TTL to use for this key when it is converted into a DNSKEY RR. If the key is imported into a zone, this is the TTL that will be used for it, unless there was @@ -134,32 +94,25 @@ is no existing DNSKEY RRset, the TTL will default to the SOA TTL. Setting the default TTL to 0 or none removes it from the key. -

    -
    +

    -h
    -
    -

    +

    Emit usage message and exit. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -v level
    -
    -

    +

    Sets the debugging level. -

    -
    +

    -E engine
    -

    +

    Specifies the cryptographic hardware to use, when applicable.

    -

    +

    When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service @@ -167,14 +120,12 @@ (--enable-native-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "--with-pkcs11".

    -
    +
    -
    - -
    +
    +

    TIMING OPTIONS

    - -

    +

    Dates can be expressed in the format YYYYMMDD or YYYYMMDDHHMMSS. If the argument begins with a '+' or '-', it is interpreted as an offset from the present time. For convenience, if such an offset @@ -184,65 +135,49 @@ days, hours, or minutes, respectively. Without a suffix, the offset is computed in seconds. To unset a date, use 'none' or 'never'.

    - -
    +
    -P date/offset
    -
    -

    +

    Sets the date on which a key is to be published to the zone. After that date, the key will be included in the zone but will not be used to sign it. -

    -
    +

    -P sync date/offset
    -
    -

    +

    Sets the date on which CDS and CDNSKEY records that match this key are to be published to the zone. -

    -
    +

    -A date/offset
    -
    -

    +

    Sets the date on which the key is to be activated. After that date, the key will be included in the zone and used to sign it. -

    -
    +

    -R date/offset
    -
    -

    +

    Sets the date on which the key is to be revoked. After that date, the key will be flagged as revoked. It will be included in the zone and will be used to sign it. -

    -
    +

    -I date/offset
    -
    -

    +

    Sets the date on which the key is to be retired. After that date, the key will still be included in the zone, but it will not be used to sign it. -

    -
    +

    -D date/offset
    -
    -

    +

    Sets the date on which the key is to be deleted. After that date, the key will no longer be included in the zone. (It may remain in the key repository, however.) -

    -
    +

    -D sync date/offset
    -
    -

    +

    Sets the date on which the CDS and CDNSKEY records that match this key are to be deleted. -

    -
    +

    -S predecessor key
    -
    -

    +

    Select a key for which the key being modified will be an explicit successor. The name, algorithm, size, and type of the predecessor key must exactly match those of the key being @@ -250,11 +185,10 @@ to the inactivation date of the predecessor. The publication date will be set to the activation date minus the prepublication interval, which defaults to 30 days. -

    -
    +

    -i interval
    -

    +

    Sets the prepublication interval for a key. If set, then the publication and activation dates must be separated by at least this much time. If the activation date is specified but the @@ -263,40 +197,34 @@ the publication date is specified but activation date isn't, then activation will be set to this much time after publication.

    -

    +

    If the key is being set to be an explicit successor to another key, then the default prepublication interval is 30 days; otherwise it is zero.

    -

    +

    As with date offsets, if the argument is followed by one of the suffixes 'y', 'mo', 'w', 'd', 'h', or 'mi', then the interval is measured in years, months, weeks, days, hours, or minutes, respectively. Without a suffix, the interval is measured in seconds.

    -
    +
    -
    - -
    +
    +

    PRINTING OPTIONS

    - -

    +

    dnssec-settime can also be used to print the timing metadata associated with a key.

    - -
    +
    -u
    -
    -

    +

    Print times in UNIX epoch format. -

    -
    +

    -p C/P/Psync/A/R/I/D/Dsync/all
    -
    -

    +

    Print a specific metadata value or set of metadata values. The -p option may be followed by one or more of the following letters or strings to indicate which value @@ -310,25 +238,17 @@ D for the deletion date, and Dsync for the CDS and CDNSKEY deletion date To print all of the metadata, use -p all. -

    -
    +

    -
    - -
    +
    +

    SEE ALSO

    - -

    - dnssec-keygen(8) - , - - dnssec-signzone(8) - , +

    dnssec-keygen(8), + dnssec-signzone(8), BIND 9 Administrator Reference Manual, RFC 5011.

    -
    - +
    @@ -349,6 +269,6 @@
    -

    BIND 9.13.2 (Development Release)

    +

    BIND 9.13.3-dev (Development Release)

    diff --git a/doc/arm/man.dnssec-signzone.html b/doc/arm/man.dnssec-signzone.html index a74775ba1285f2096859a08a9dd1a76146d551a1..9d3ab2024c528fe10142fab8a66ee78a200f1dac 100644 --- a/doc/arm/man.dnssec-signzone.html +++ b/doc/arm/man.dnssec-signzone.html @@ -10,7 +10,7 @@ dnssec-signzone - + @@ -32,70 +32,17 @@
    - - - - - -
    +

    Name

    -

    - dnssec-signzone - — DNSSEC zone signing tool -

    +

    dnssec-signzone — DNSSEC zone signing tool

    - - - -
    +

    Synopsis

    -

    - dnssec-signzone - [-a] - [-c class] - [-d directory] - [-D] - [-E engine] - [-e end-time] - [-f output-file] - [-g] - [-h] - [-i interval] - [-I input-format] - [-j jitter] - [-K directory] - [-k key] - [-L serial] - [-l domain] - [-M maxttl] - [-N soa-serial-format] - [-o origin] - [-O output-format] - [-P] - [-Q] - [-R] - [-S] - [-s start-time] - [-T ttl] - [-t] - [-u] - [-v level] - [-V] - [-X extended end-time] - [-x] - [-z] - [-3 salt] - [-H iterations] - [-A] - {zonefile} - [key...] -

    -
    - -
    +

    dnssec-signzone [-a] [-c class] [-d directory] [-D] [-E engine] [-e end-time] [-f output-file] [-g] [-h] [-i interval] [-I input-format] [-j jitter] [-K directory] [-k key] [-L serial] [-l domain] [-M maxttl] [-N soa-serial-format] [-o origin] [-O output-format] [-P] [-Q] [-R] [-S] [-s start-time] [-T ttl] [-t] [-u] [-v level] [-V] [-X extended end-time] [-x] [-z] [-3 salt] [-H iterations] [-A] {zonefile} [key...]

    +
    +

    DESCRIPTION

    - -

    dnssec-signzone +

    dnssec-signzone signs a zone. It generates NSEC and RRSIG records and produces a signed version of the zone. The security status of delegations from the signed zone @@ -103,46 +50,34 @@ determined by the presence or absence of a keyset file for each child zone.

    -
    - -
    +
    +

    OPTIONS

    - - -
    +
    -a
    -
    -

    +

    Verify all generated signatures. -

    -
    +

    -c class
    -
    -

    +

    Specifies the DNS class of the zone. -

    -
    +

    -C
    -
    -

    +

    Compatibility mode: Generate a keyset-zonename file in addition to dsset-zonename when signing a zone, for use by older versions of dnssec-signzone. -

    -
    +

    -d directory
    -
    -

    +

    Look for dsset- or keyset- files in directory. -

    -
    +

    -D
    -
    -

    +

    Output only those record types automatically managed by dnssec-signzone, i.e. RRSIG, NSEC, NSEC3 and NSEC3PARAM records. If smart signing @@ -151,16 +86,15 @@ zone file with $INCLUDE. This option cannot be combined with -O raw, -O map, or serial number updating. -

    -
    +

    -E engine
    -

    +

    When applicable, specifies the hardware to use for cryptographic operations, such as a secure key store used for signing.

    -

    +

    When BIND is built with OpenSSL PKCS#11 support, this defaults to the string "pkcs11", which identifies an OpenSSL engine that can drive a cryptographic accelerator or hardware service @@ -168,39 +102,30 @@ (--enable-native-pkcs11), it defaults to the path of the PKCS#11 provider library specified via "--with-pkcs11".

    -
    +
    -g
    -
    -

    +

    Generate DS records for child zones from dsset- or keyset- file. Existing DS records will be removed. -

    -
    +

    -K directory
    -
    -

    +

    Key repository: Specify a directory to search for DNSSEC keys. If not specified, defaults to the current directory. -

    -
    +

    -k key
    -
    -

    +

    Treat specified key as a key signing key ignoring any key flags. This option may be specified multiple times. -

    -
    +

    -l domain
    -
    -

    +

    Generate a DLV set in addition to the key (DNSKEY) and DS sets. The domain is appended to the name of the records. -

    -
    +

    -M maxttl
    -
    -

    +

    Sets the maximum TTL for the signed zone. Any TTL higher than maxttl in the input zone will be reduced to maxttl @@ -213,11 +138,9 @@ max-zone-ttl in named.conf. (Note: This option is incompatible with -D, because it modifies non-DNSSEC data in the output zone.) -

    -
    +

    -s start-time
    -
    -

    +

    Specify the date and time when the generated RRSIG records become valid. This can be either an absolute or relative time. An absolute start time is indicated by a number @@ -226,11 +149,9 @@ indicated by +N, which is N seconds from the current time. If no start-time is specified, the current time minus 1 hour (to allow for clock skew) is used. -

    -
    +

    -e end-time
    -
    -

    +

    Specify the date and time when the generated RRSIG records expire. As with start-time, an absolute time is indicated in YYYYMMDDHHMMSS notation. A time relative @@ -240,11 +161,10 @@ specified, 30 days from the start time is used as a default. end-time must be later than start-time. -

    -
    +

    -X extended end-time
    -

    +

    Specify the date and time when the generated RRSIG records for the DNSKEY RRset will expire. This is to be used in cases when the DNSKEY signatures need to persist longer than @@ -252,7 +172,7 @@ of the KSK is kept offline and the KSK signature is to be refreshed manually.

    -

    +

    As with start-time, an absolute time is indicated in YYYYMMDDHHMMSS notation. A time relative to the start time is indicated with +N, which is N seconds from @@ -263,34 +183,28 @@ 30 days from the start time.) extended end-time must be later than start-time.

    -
    +
    -f output-file
    -
    -

    +

    The name of the output file containing the signed zone. The default is to append .signed to the input filename. If output-file is set to "-", then the signed zone is written to the standard output, with a default output format of "full". -

    -
    +

    -h
    -
    -

    +

    Prints a short summary of the options and arguments to dnssec-signzone. -

    -
    +

    -V
    -
    -

    +

    Prints version information. -

    -
    +

    -i interval
    -

    +

    When a previously-signed zone is passed as input, records may be resigned. The interval option specifies the cycle interval as an offset from the current @@ -298,7 +212,7 @@ cycle