mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-22 10:10:06 +00:00
Code Issues Releases Wiki Activity
bind/doc/arm/general.rst

484 lines
18 KiB
ReStructuredText
Raw Normal View History

Update the copyright information in all files in the repository This commit converts the license handling to adhere to the REUSE specification. It specifically: 1. Adds used licnses to LICENSES/ directory 2. Add "isc" template for adding the copyright boilerplate 3. Changes all source files to include copyright and SPDX license header, this includes all the C sources, documentation, zone files, configuration files. There are notes in the doc/dev/copyrights file on how to add correct headers to the new files. 4. Handle the rest that can't be modified via .reuse/dep5 file. The binary (or otherwise unmodifiable) files could have license places next to them in <foo>.license file, but this would lead to cluttered repository and most of the files handled in the .reuse/dep5 file are system test files.
2021-06-03 08:37:05 +02:00
.. Copyright (C) Internet Systems Consortium, Inc. ("ISC")
..
.. SPDX-License-Identifier: MPL-2.0
..
.. 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 https://mozilla.org/MPL/2.0/.
..
.. See the COPYRIGHT file distributed with this work for additional
.. information regarding copyright ownership.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
.. General:
General DNS Reference Information
=================================
.. _ipv6addresses:
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
IPv6 Addresses (AAAA)
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
---------------------
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
IPv6 addresses are 128-bit identifiers, for interfaces and sets of
interfaces, which were introduced in the DNS to facilitate scalable
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Internet routing. There are three types of addresses: *Unicast*, an
identifier for a single interface; *Anycast*, an identifier for a set of
interfaces; and *Multicast*, an identifier for a set of interfaces. Here
we describe the global Unicast address scheme. For more information, see
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3587`, "IPv6 Global Unicast Address Format."
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
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,
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
and roughly corresponds to the IPv4 *network* section of the address
range. The subnet identifier is for local subnetting, much like
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
subnetting an IPv4 /16 network into /24 subnets. The interface
identifier is the address of an individual 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
Final text edits to BIND 9 ARM in this round of updates
2020-07-02 16:54:57 +00:00
IPv4; subnetting can be carried out on bit boundaries, in much the same
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
way as Classless InterDomain Routing (CIDR), and the DNS PTR
representation ("nibble" format) makes setting up reverse zones easier.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
The interface identifier must be unique on the local link, and is
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
usually generated automatically by the IPv6 implementation, although it
is usually possible to override the default setting if necessary. A
typical IPv6 address might look like:
Final text edits to BIND 9 ARM in this round of updates
2020-07-02 16:54:57 +00:00
``2001:db8:201:9:a00:20ff:fe81:2b32``.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
IPv6 address specifications often contain long strings of zeros, so the
architects have included a shorthand for specifying them. The double
colon (``::``) indicates the longest possible string of zeros that can
fit, and can be used only once in an address.
.. _bibliography:
Bibliography (and Suggested Reading)
------------------------------------
.. _rfcs:
Fix typos and change http to https Fixed minor typographical errors and changed URLs from "http" to "https" where appropriate.
2020-09-14 21:04:19 +00:00
Requests for Comment (RFCs)
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
~~~~~~~~~~~~~~~~~~~~~~~~~~~
Reword RFC section in the ARM Add couple links and caveant for uninitiated readers.
2022-01-20 17:04:00 +01:00
Specification documents for the Internet protocol suite, including the
DNS, are published as part of the `Request for Comments`_ (RFCs) series
of technical notes. The standards themselves are defined by the
`Internet Engineering Task Force`_ (IETF) and the `Internet Engineering
Steering Group`_ (IESG). RFCs can be viewed online at:
https://www.rfc-editor.org/.
While reading RFCs, please keep in mind that :rfc:`not all RFCs are
standards <1796>`, and also that the validity of documents does change
over time. Every RFC needs to be interpreted in the context of other
documents.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
BIND 9 strives for strict compliance with IETF standards. To the best
of our knowledge, BIND 9 complies with the following RFCs, with
the caveats and exceptions listed in the numbered notes below. Many
of these RFCs were written by current or former ISC staff members.
The list is non-exhaustive.
Reword RFC section in the ARM Add couple links and caveant for uninitiated readers.
2022-01-20 17:04:00 +01:00
.. _Internet Engineering Steering Group: https://www.ietf.org/about/groups/iesg/
.. _Internet Engineering Task Force: https://www.ietf.org/about/
.. _Request for Comments: https://www.ietf.org/standards/rfcs/
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Some of these RFCs, though DNS-related, are not concerned with implementing
software.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Internet Standards
------------------
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1034` - P. Mockapetris. *Domain Names — Concepts and Facilities.* November
1987.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1035` - P. Mockapetris. *Domain Names — Implementation and Specification.*
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
November 1987. [#rfc1035_1]_ [#rfc1035_2]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1123` - R. Braden. *Requirements for Internet Hosts - Application and
Support.* October 1989.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3596` - S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. *DNS Extensions to
Support IP Version 6.* October 2003.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5011` - M. StJohns. *Automated Updates of DNS Security (DNSSEC) Trust Anchors.*
:rfc:`6891` - J. Damas, M. Graff, and P. Vixie. *Extension Mechanisms for DNS
(EDNS(0)).* April 2013.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
.. _proposed_standards:
Proposed Standards
------------------
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1982` - R. Elz and R. Bush. *Serial Number Arithmetic.* August 1996.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`1995` - M. Ohta. *Incremental Zone Transfer in DNS.* August 1996.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1996` - P. Vixie. *A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY).*
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
August 1996.
:rfc:`2136` - P. Vixie, S. Thomson, Y. Rekhter, and J. Bound. *Dynamic Updates in the
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Domain Name System (DNS UPDATE).* April 1997.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`2163` - A. Allocchio. *Using the Internet DNS to Distribute MIXER
Conformant Global Address Mapping (MCGAM).* January 1998.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`2181` - R. Elz and R. Bush. *Clarifications to the DNS Specification.* July 1997.
:rfc:`2308` - M. Andrews. *Negative Caching of DNS Queries (DNS NCACHE).* March 1998.
:rfc:`2539` - D. Eastlake, 3rd. *Storage of Diffie-Hellman Keys in the Domain Name
System (DNS).* March 1999.
:rfc:`2782` - A. Gulbrandsen, P. Vixie, and L. Esibov. *A DNS RR for Specifying the
Location of Services (DNS SRV).* February 2000.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`2845` - P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington. *Secret Key
Transaction Authentication for DNS (TSIG).* May 2000.
:rfc:`2930` - D. Eastlake, 3rd. *Secret Key Establishment for DNS (TKEY RR).*
September 2000.
:rfc:`2931` - D. Eastlake, 3rd. *DNS Request and Transaction Signatures (SIG(0)s).*
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
September 2000. [#rfc2931]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`3007` - B. Wellington. *Secure Domain Name System (DNS) Dynamic Update.*
November 2000.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3110` - D. Eastlake, 3rd. *RSA/SHA-1 SIGs and RSA KEYs in the Domain Name
System (DNS).* May 2001.
Fix two RFCs that were out of numerical order
2020-06-10 19:15:52 +00:00
:rfc:`3225` - D. Conrad. *Indicating Resolver Support of DNSSEC.* December 2001.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3226` - O. Gudmundsson. *DNSSEC and IPv6 A6 Aware Server/Resolver
Message Size Requirements.* December 2001.
Fix two RFCs that were out of numerical order
2020-06-10 19:15:52 +00:00
:rfc:`3492` - A. Costello. *Punycode: A Bootstring Encoding of Unicode for
Internationalized Domain Names in Applications (IDNA).* March 2003.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3597` - A. Gustafsson. *Handling of Unknown DNS Resource Record (RR) Types.*
September 2003.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`3645` - 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.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4025` - M. Richardson. *A Method for Storing IPsec Keying Material in
DNS.* March 2005.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`4033` - R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. *DNS Security
Fix incorrect RFC footnote about A6 RR type in RFC4033 A6 type is not mentioned anywhere in RFC4033.
2022-01-21 13:46:49 +01:00
Introduction and Requirements.* March 2005.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`4034` - R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. *Resource Records for
the DNS Security Extensions.* March 2005.
:rfc:`4035` - R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. *Protocol
Modifications for the DNS Security Extensions.* March 2005.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4255` - J. Schlyter and W. Griffin. *Using DNS to Securely Publish Secure
Shell (SSH) Key Fingerprints.* January 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4343` - D. Eastlake, 3rd. *Domain Name System (DNS) Case Insensitivity
Clarification.* January 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4398` - S. Josefsson. *Storing Certificates in the Domain Name System (DNS).* March 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Fix various typos in the documentation Generally, the issues fixed here are missing articles, wrong articles and double articles. We especially like "the the".
2020-12-16 10:24:01 +01:00
:rfc:`4470` - S. Weiler and J. Ihren. *Minimally covering NSEC Records and
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
DNSSEC On-line Signing.* April 2006. [#rfc4470]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4509` - W. Hardaker. *Use of SHA-256 in DNSSEC Delegation Signer
(DS) Resource Records (RRs).* May 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4592` - E. Lewis. *The Role of Wildcards in the Domain Name System.* July 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4635` - D. Eastlake, 3rd. *HMAC SHA (Hashed Message Authentication
Code, Secure Hash Algorithm) TSIG Algorithm Identifiers.* August 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4701` - M. Stapp, T. Lemon, and A. Gustafsson. *A DNS Resource Record
(RR) for Encoding Dynamic Host Configuration Protocol (DHCP) Information (DHCID
RR).* October 2006.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
:rfc:`4955` - D. Blacka. *DNS Security (DNSSEC) Experiments.* July 2007. [#rfc4955]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5001` - R. Austein. *DNS Name Server Identifier (NSID) Option.* August 2007.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5155` - B. Laurie, G. Sisson, R. Arends, and D. Blacka. *DNS Security
(DNSSEC) Hashed Authenticated Denial of Existence.* March 2008.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5452` - A. Hubert and R. van Mook. *Measures for Making DNS More
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Resilient Against Forged Answers.* January 2009. [#rfc5452]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5702` - J. Jansen. *Use of SHA-2 Algorithms with RSA in DNSKEY and
RRSIG Resource Records for DNSSEC.* October 2009.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Add newer version of IDNA RFC to docs
2022-02-09 16:21:29 +01:00
:rfc:`5891` - J. Klensin.
*Internationalized Domain Names in Applications (IDNA): Protocol.*
August 2010
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5936` - E. Lewis and A. Hoenes, Ed. *DNS Zone Transfer Protocol (AXFR).*
June 2010.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5952` - S. Kawamura and M. Kawashima. *A Recommendation for IPv6 Address
Text Representation.* August 2010.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6052` - C. Bao, C. Huitema, M. Bagnulo, M. Boucadair, and X. Li. *IPv6
Addressing of IPv4/IPv6 Translators.* October 2010.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6147` - M. Bagnulo, A. Sullivan, P. Matthews, and I. van Beijnum.
*DNS64: DNS Extensions for Network Address Translation from IPv6 Clients to
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
IPv4 Servers.* April 2011. [#rfc6147]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6604` - D. Eastlake, 3rd. *xNAME RCODE and Status Bits Clarification.*
April 2012.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6605` - P. Hoffman and W. C. A. Wijngaards. *Elliptic Curve Digital
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Signature Algorithm (DSA) for DNSSEC.* April 2012. [#rfc6605]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6672` - S. Rose and W. Wijngaards. *DNAME Redirection in the DNS.*
June 2012.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6698` - P. Hoffman and J. Schlyter. *The DNS-Based Authentication of
Named Entities (DANE) Transport Layer Security (TLS) Protocol: TLSA.*
August 2012.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6725` - S. Rose. *DNS Security (DNSSEC) DNSKEY Algorithm IANA Registry
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Updates.* August 2012. [#rfc6725]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6840` - S. Weiler, Ed., and D. Blacka, Ed. *Clarifications and
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Implementation Notes for DNS Security (DNSSEC).* February 2013. [#rfc6840]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
:rfc:`7050` - T. Savolainen, J. Korhonen, and D. Wing. *Discovery of the IPv6
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Prefix Used for IPv6 Address Synthesis.* November 2013. [#rfc7050]_
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7344` - W. Kumari, O. Gudmundsson, and G. Barwood. *Automating DNSSEC
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Delegation Trust Maintenance.* September 2014. [#rfc7344]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7477` - W. Hardaker. *Child-to-Parent Synchronization in DNS.* March
2015.
:rfc:`7766` - J. Dickinson, S. Dickinson, R. Bellis, A. Mankin, and D.
Wessels. *DNS Transport over TCP - Implementation Requirements.* March 2016.
:rfc:`7828` - P. Wouters, J. Abley, S. Dickinson, and R. Bellis.
*The edns-tcp-keepalive EDNS0 Option.* April 2016.
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
:rfc:`7830` - A. Mayrhofer. *The EDNS(0) Padding Option.* May 2016. [#rfc7830]_
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
:rfc:`8078` - O. Gudmundsson and P. Wouters. *Managing DS Records from the
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Parent via CDS/CDNSKEY.* March 2017. [#rfc8078]_
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`8080` - O. Sury and R. Edmonds. *Edwards-Curve Digital Security Algorithm
(EdDSA) for DNSSEC.* February 2017.
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
:rfc:`8880` - S. Cheshire and D. Schinazi. *Special Use Domain Name
'ipv4only.arpa'.* August 2020.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`8624` - P. Wouters and O. Sury. *Algorithm Implementation Requirements
and Usage Guidance for DNSSEC.* June 2019.
Replace obsolete RFC6488 reference with RFC8659 (CAA)
2022-02-09 16:14:43 +01:00
:rfc:`8659` - P. Hallam-Baker, R. Stradling, and J. Hoffman-Andrews.
*DNS Certification Authority Authorization (CAA) Resource Record.*
November 2019.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`8749` - W. Mekking and D. Mahoney. *Moving DNSSEC Lookaside Validation
(DLV) to Historic Status.* March 2020.
Informational RFCs
------------------
:rfc:`1535` - E. Gavron. *A Security Problem and Proposed Correction With Widely
Deployed DNS Software.* October 1993.
:rfc:`1536` - A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller. *Common DNS
Implementation Errors and Suggested Fixes.* October 1993.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1706` - B. Manning and R. Colella. *DNS NSAP Resource Records.* October 1994.
:rfc:`1912` - D. Barr. *Common DNS Operational and Configuration Errors.* February
1996.
:rfc:`2230` - R. Atkinson. *Key Exchange Delegation Record for the DNS.* November
1997.
:rfc:`3363` - R. Bush, A. Durand, B. Fink, O. Gudmundsson, and T. Hain.
*Representing Internet Protocol Version 6 (IPv6) Addresses in the Domain Name
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
System (DNS).* August 2002. [#rfc3363]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3493` - R. Gilligan, S. Thomson, J. Bound, J. McCann, and W. Stevens.
*Basic Socket Interface Extensions for IPv6.* March 2003.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3496` - A. G. Malis and T. Hsiao. *Protocol Extension for Support of
Asynchronous Transfer Mode (ATM) Service Class-aware Multiprotocol Label
Switching (MPLS) Traffic Engineering.* March 2003.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3833` - D. Atkins and R. Austein. *Threat Analysis of the Domain Name System
(DNS).* August 2004.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4074` - Y. Morishita and T. Jinmei. *Common Misbehavior Against DNS Queries for
IPv6 Addresses.* June 2005.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4892` - S. Woolf and D. Conrad. *Requirements for a Mechanism
Identifying a Name Server Instance.* June 2007.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6781` - O. Kolkman, W. Mekking, and R. Gieben. *DNSSEC Operational
Practices, Version 2.* December 2012.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7043` - J. Abley. *Resource Records for EUI-48 and EUI-64 Addresses
in the DNS.* October 2013.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7129` - R. Gieben and W. Mekking. *Authenticated Denial of Existence
in the DNS.* February 2014.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7553` - P. Faltstrom and O. Kolkman. *The Uniform Resource Identifier
(URI) DNS Resource Record.* June 2015.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7583` - S. Morris, J. Ihren, J. Dickinson, and W. Mekking. *DNSSEC Key
Rollover Timing Considerations.* October 2015.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Experimental RFCs
-----------------
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1183` - C. F. Everhart, L. A. Mamakos, R. Ullmann, P. Mockapetris. *New DNS RR
Definitions.* October 1990.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1712` - C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni. *DNS Encoding of
Geographical Location.* November 1994.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1876` - C. Davis, P. Vixie, T. Goodwin, and I. Dickinson. *A Means for Expressing
Location Information in the Domain Name System.* January 1996.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`3123` - P. Koch. *A DNS RR Type for Lists of Address Prefixes (APL RR).* June
2001.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
:rfc:`5205` - P. Nikander and J. Laganier. *Host Identity Protocol (HIP)
Domain Name System (DNS) Extension.* April 2008.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6742` - RJ Atkinson, SN Bhatti, U. St. Andrews, and S. Rose. *DNS
Resource Records for the Identifier-Locator Network Protocol (ILNP).*
November 2012.
:rfc:`7314` - M. Andrews. *Extension Mechanisms for DNS (EDNS) EXPIRE Option.*
July 2014.
:rfc:`7929` - P. Wouters. *DNS-Based Authentication of Named Entities (DANE)
Bindings for OpenPGP.* August 2016.
Best Current Practice RFCs
--------------------------
:rfc:`2219` - M. Hamilton and R. Wright. *Use of DNS Aliases for Network Services.*
October 1997.
:rfc:`2317` - H. Eidnes, G. de Groot, and P. Vixie. *Classless IN-ADDR.ARPA Delegation.*
March 1998.
:rfc:`2606` - D. Eastlake, 3rd and A. Panitz. *Reserved Top Level DNS Names.* June
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
1999. [#rfc2606]_
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`3901` - A. Durand and J. Ihren. *DNS IPv6 Transport Operational Guidelines.*
September 2004.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`5625` - R. Bellis. *DNS Proxy Implementation Guidelines.* August 2009.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`6303` - M. Andrews. *Locally Served DNS Zones.* July 2011.
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`7793` - M. Andrews. *Adding 100.64.0.0/10 Prefixes to the IPv4
Locally-Served DNS Zones Registry.* May 2016.
Accidentally wrote RFC8096 instead of 8906
2020-09-23 19:41:58 +00:00
:rfc:`8906` - M. Andrews and R. Bellis. *A Common Operational Problem in DNS
Add RFC8096 to list in doc/arm/general.rst
2020-09-23 19:34:42 +00:00
Servers: Failure to Communicate.* September 2020.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Historic RFCs
-------------
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
:rfc:`2874` - M. Crawford and C. Huitema. *DNS Extensions to Support IPv6 Address
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
Aggregation and Renumbering.* July 2000. [#rfc2874]_
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`4431` - M. Andrews and S. Weiler. *The DNSSEC Lookaside Validation
(DLV) DNS Resource Record.* February 2006.
RFCs of Type "Unknown"
----------------------
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
:rfc:`1101` - P. Mockapetris. *DNS Encoding of Network Names and Other Types.*
April 1989.
Notes
Fix miscellaneous little bugs in RST formatting
2020-06-29 19:39:03 +02:00
~~~~~
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc1035_1] Queries to zones that have failed to load return SERVFAIL rather
than a non-authoritative response. This is considered a feature.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc1035_2] CLASS ANY queries are not supported. This is considered a
feature.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc2931] When receiving a query signed with a SIG(0), the server is
only able to verify the signature if it has the key in its local
authoritative data; it cannot do recursion or validation to
retrieve unknown keys.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc2874] Compliance is with loading and serving of A6 records only.
A6 records were moved to the experimental category by :rfc:`3363`.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc4470] Minimally Covering NSEC records are accepted but not generated.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc4955] BIND 9 interoperates with correctly designed experiments.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc5452] ``named`` only uses ports to extend the ID space; addresses are not
used.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc6147] Section 5.5 does not match reality. ``named`` uses the presence
of DO=1 to detect if validation may be occurring. CD has no bearing
on whether validation occurs.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc6605] Compliance is conditional on the OpenSSL library being linked against
a supporting ECDSA.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc6725] RSAMD5 support has been removed. See :rfc:`6944`.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc6840] Section 5.9 - Always set CD=1 on queries. This is *not* done, as
it prevents DNSSEC from working correctly through another recursive server.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
When talking to a recursive server, the best algorithm is to send
CD=0 and then send CD=1 iff SERVFAIL is returned, in case the recursive
server has a bad clock and/or bad trust anchor. Alternatively, one
can send CD=1 then CD=0 on validation failure, in case the recursive
server is under attack or there is stale/bogus authoritative data.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc7344] Updating of parent zones is not yet implemented.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc7830] ``named`` does not currently encrypt DNS requests, so the PAD option
is accepted but not returned in responses.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc3363] Section 4 is ignored.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc2606] This does not apply to DNS server implementations.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc1521] Only the Base 64 encoding specification is supported.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#idna] BIND 9 requires ``--with-libidn2`` to enable entry of IDN labels within
dig, host, and nslookup at compile time. ACE labels are supported
everywhere with or without ``--with-libidn2``.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc4294] Section 5.1 - DNAME records are fully supported.
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc7050] RFC 7050 is updated by RFC 8880.
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
Use Sphinx footnotes for DNS Reference Information It limits risk of errors while doing updates, which are next in the pipeline.
2022-01-21 17:15:32 +01:00
.. [#rfc8078] Updating of parent zones is not yet implemented.
Add RFCs listed in doc/misc/rfc-compliance to doc/arm/general.rst There were three RFCs listed in list of "RFCs we implement" but missing in the ARM. Command to compare lists in the two documents: diff <(grep -o '^ RFC[0-9]\+' doc/misc/rfc-compliance | sed -e 's/[^0-9]//g' | sort -n) <(grep '^:rfc:`' doc/arm/general.rst | sed -e 's/^.*`\([0-9]*\)`.*$/\1/' | sort -n)
2022-01-20 14:07:25 +01:00
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
.. _internet_drafts:
Internet Drafts
~~~~~~~~~~~~~~~
Internet Drafts (IDs) are rough-draft working documents of the Internet
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
Engineering Task Force (IETF). They are, in essence, RFCs in the preliminary
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
stages of development. Implementors are cautioned not to regard IDs as
archival, and they should not be quoted or cited in any formal documents
unless accompanied by the disclaimer that they are "works in progress."
Content, clarity, grammar updates to general.rst This includes reorganization of the lists of RFCs supported by BIND 9. I included all the RFCs and notes from the list identified by Vicky in any DNS-related RFCs written by current ISC engineers, on the assumption that BIND would comply with them.
2020-06-01 21:54:04 +00:00
IDs have a lifespan of six months, after which they are deleted unless
Convert the documentation to Sphinx documentation format The ARM and the manpages have been converted into Sphinx documentation format. Sphinx uses reStructuredText as its markup language, and many of its strengths come from the power and straightforwardness of reStructuredText and its parsing and translating suite, the Docutils.
2019-03-31 12:49:47 +02:00
updated by their authors.
Reference in New Issue Copy Permalink