DNS Catalog Zones
draft-ietf-dnsop-dns-catalog-zones-01
DNSOP Working Group P. van Dijk
Internet-Draft PowerDNS
Intended status: Standards Track L. Peltan
Expires: 7 June 2021 CZ.NIC
O. Sury
Internet Systems Consortium
W. Toorop
NLnet Labs
L. Vandewoestijne
4 December 2020
DNS Catalog Zones
draft-ietf-dnsop-dns-catalog-zones-01
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 7 June 2021.
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 carefully, as they describe your rights
van Dijk, et al. Expires 7 June 2021 [Page 1]
Internet-Draft dns-catalog-zones December 2020
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 . . . . . . . . . . . . . . . . . . 5
5. The Serial Property . . . . . . . . . . . . . . . . . . . . . 6
5.1. The SERIAL Resource Record . . . . . . . . . . . . . . . 7
5.2. SERIAL RDATA Wire Format . . . . . . . . . . . . . . . . 7
5.2.1. The Serial Field . . . . . . . . . . . . . . . . . . 7
5.3. SERIAL Presentation Format . . . . . . . . . . . . . . . 7
5.4. SERIAL RR Usage - option 1 . . . . . . . . . . . . . . . 7
5.5. SERIAL RR Usage - option 2 . . . . . . . . . . . . . . . 8
5.6. Serial property as TXT RR - option 3 . . . . . . . . . . 8
6. Nameserver Behavior . . . . . . . . . . . . . . . . . . . . . 8
6.1. General Requirements . . . . . . . . . . . . . . . . . . 8
7. Updating Catalog Zones . . . . . . . . . . . . . . . . . . . 10
7.1. Implementation Notes . . . . . . . . . . . . . . . . . . 10
8. Implementation Status . . . . . . . . . . . . . . . . . . . . 10
9. Security Considerations . . . . . . . . . . . . . . . . . . . 11
10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 11
12. Normative References . . . . . . . . . . . . . . . . . . . . 12
13. Informative References . . . . . . . . . . . . . . . . . . . 13
Appendix A. Change History (to be removed before final
publication) . . . . . . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
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
Show full document text