DIG-BIND9.17.15.x64-for Windows

<!-- - Copyright (C) Internet Systems Consortium, Inc. ("ISC") - - This Source Code Form is subject to the terms of the Mozilla Public - License, v. 2.0. If a copy of the MPL was not distributed with this - file, You can obtain one at http://mozilla.org/MPL/2.0/. - - See the COPYRIGHT file distributed with this work for additional - information regarding copyright ownership. --> # BIND 9 ### Contents 1. [Introduction](#intro) 1. [Reporting bugs and getting help](#help) 1. [Contributing to BIND](#contrib) 1. [Building BIND](#build) 1. [macOS](#macos) 1. [Dependencies](#dependencies) 1. [Compile-time options](#opts) 1. [Automated testing](#testing) 1. [Documentation](#doc) 1. [Change log](#changes) 1. [Acknowledgments](#ack) ### <a name="intro"/> Introduction BIND (Berkeley Internet Name Domain) is a complete, highly portable implementation of the Domain Name System (DNS) protocol. The BIND name server, `named`, can act 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 rewrite of the BIND architecture that was used in versions 4 and 8. Internet Systems Consortium ([https://www.isc.org](https://www.isc.org)), a 501(c)(3) US 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 licensed 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](HISTORY.md). For a detailed list of changes made throughout the history of BIND 9, see the file [CHANGES](CHANGES). See [below](#changes) for details on the CHANGES file format. For up-to-date versions and release notes, see [https://www.isc.org/download/](https://www.isc.org/download/). For information about supported platforms, see [PLATFORMS](PLATFORMS.md). ### <a name="help"/> 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](https://gitlab.isc.org) at [https://gitlab.isc.org/isc-projects/bind9](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 you are reporting a bug that is a potential security issue, such as an assertion failure or other crash in `named`, please do *NOT* use GitLab to report it. Instead, send mail to [security-officer@isc.org](mailto:security-officer@isc.org) using our OpenPGP key to secure your message. (Information about OpenPGP and links to our key can be found at [https://www.isc.org/pgpkey](https://www.isc.org/pgpkey).) Please do not discuss the bug on any public mailing list. For a general overview of ISC security policies, read the Knowledgebase article at [https://kb.isc.org/docs/aa-00861](https://kb.isc.org/docs/aa-00861). Professional support and training for BIND are available from ISC. Contact us at [https://www.isc.org/contact](https://www.isc.org/contact) for more information. To join the __BIND Users__ mailing list, or view the archives, visit [https://lists.isc.org/mailman/listinfo/bind-users](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](https://lists.isc.org/mailman/listinfo/bind-workers). ### <a name="contrib"/> Contributing to BIND ISC maintains a public git repository for BIND; details can be found at [https://www.isc.org/sourceaccess/](https://www.isc.org/sourceaccess/). Information for BIND contributors can be found in the following files: - General information: [CONTRIBUTING.md](CONTRIBUTING.md) - Code of Conduct: [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) - BIND 9 code style: [doc/dev/style.md](doc/dev/style.md) - BIND architecture and developer guide: [doc/dev/dev.md](doc/dev/dev.md) Patches for BIND may be submitted as [merge requests](https://gitlab.isc.org/isc-projects/bind9/merge_requests) on the [ISC GitLab server](https://gitlab.isc.org). By default, external contributors do not have the ability to fork BIND on the GitLab server; 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](https://gitlab.isc.org/isc-projects/bind9/issues) and including your patch as an attachment, preferably generated by `git format-patch`. ### <a name="build"/> Building BIND 9 At a minimum, BIND requires a Unix or Linux system with an ANSI C compiler, basic POSIX support, and a 64-bit integer type. BIND also requires the `libuv` asynchronous I/O library, the `nghttp2` HTTP/2 library, and 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](#opts) below for details on other libraries that may be required to support optional features. Successful builds have been observed on many versions of Linux and Unix, including RHEL/CentOS, Fedora, Debian, Ubuntu, SLES, openSUSE, Slackware, Alpine, FreeBSD, NetBSD, OpenBSD, macOS, Solaris, OpenIndiana, OmniOS CE, HP-UX, and OpenWRT. BIND 9 is also available for Windows Server 2012 R2 and higher. See `win32utils/build.txt` for details on building for Windows systems. To build on a Unix or Linux system, use: $ autoreconf -fi (if you are building in the git repository) $ ./configure $ make If you're using Emacs, you might find `make tags` helpful. Several environment variables, which can be set before running `configure`, affect compilation. Significant ones are: |Variable|Description | |--------------------|-----------------------------------------------| |`CC`|The C compiler to use. `configure` tries to figure out the right one for supported systems.| |`CFLAGS`|C compiler flags. Defaults to include -g and/or -O2 as supported by the compiler. Please include '-g' if you need to set `CFLAGS`. | |`LDFLAGS`|Linker flags. Defaults to empty string.| Additional environment variables affecting the build are listed at the end of the `configure` help text, which can be obtained by running the command: $ ./configure --help #### <a name="macos"> macOS Building on macOS assumes that the "Command Tools for Xcode" are installed. These can be downloaded from [https://developer.apple.com/download/more/](https://developer.apple.com/download/more/) or, if you have Xcode already installed, you can run `xcode-select --install`. (Note that an Apple ID may be required to access the download page.) #### <a name="dependencies"> Dependencies