DNS Catalog Zones
draft-ietf-dnsop-dns-catalog-zones-00
DNSOP Working Group P. van Dijk
Internet-Draft PowerDNS
Intended status: Standards Track L. Peltan
Expires: December 5, 2020 CZ.NIC
O. Sury
Internet Systems Consortium
W. Toorop
NLnet Labs
L. Vandewoestijne
June 3, 2020
DNS Catalog Zones
draft-ietf-dnsop-dns-catalog-zones-00
Abstract
This document describes a method for automatic DNS zone provisioning
among DNS primary and secondary nameservers by storing and
transferring the catalog of zones to be provisioned as one or more
regular DNS zones.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 5, 2020.
Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
van Dijk, et al. Expires December 5, 2020 [Page 1]
Internet-Draft dns-catalog-zones June 2020
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
3. Description . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Catalog Zone Structure . . . . . . . . . . . . . . . . . . . 4
4.1. SOA and NS Records . . . . . . . . . . . . . . . . . . . 4
4.2. Catalog Zone Schema Version . . . . . . . . . . . . . . . 4
4.3. List of Member Zones . . . . . . . . . . . . . . . . . . 4
5. Nameserver Behavior . . . . . . . . . . . . . . . . . . . . . 5
5.1. General Requirements . . . . . . . . . . . . . . . . . . 5
6. Updating Catalog Zones . . . . . . . . . . . . . . . . . . . 7
6.1. Implementation Notes . . . . . . . . . . . . . . . . . . 7
7. Security Considerations . . . . . . . . . . . . . . . . . . . 7
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
10.1. Normative References . . . . . . . . . . . . . . . . . . 8
10.2. Informative References . . . . . . . . . . . . . . . . . 9
Appendix A. Change History (to be removed before final
publication) . . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 10
1. Introduction
The data in a DNS zone is synchronized amongst its primary and
secondary nameservers using AXFR and IXFR. However, the list of
zones served by the primary (called a catalog in [RFC1035]) is not
automatically synchronized with the secondaries. To add or remove a
zone, the administrator of a DNS nameserver farm not only has to add
or remove the zone from the primary, they must also add/remove the
zone from all secondaries, either manually or via an external
application. This can be both inconvenient and error-prone; it is
also dependent on the nameserver implementation.
This document describes a method in which the catalog is represented
as a regular DNS zone (called a "catalog zone" here), and transferred
using DNS zone transfers. As zones are added to or removed from the
catalog zone, the changes are propagated to the secondary nameservers
Show full document text