Updates to Locally Served DNS Zones and IP Special-Purpose Address Space Registries

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 3 September 2026.¶

Copyright Notice

Copyright (c) 2026 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 and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

[RFC6303] "Locally Served DNS Zones", it defines two IANA registries called "IPv4 Locally-Served DNS Zone" and "IPv6 Locally-Served DNS Zone" registries. This document changes the registration policy for that registry from "IETF Review" to "Expert Review".¶

Also, this document updates IP Special-Purpose Address Space registries {{!RFC6890}} to indicate whether an IP address block is eligible to be in Locally-Served DNS Zones. This change is meant to ensure consistent registrations between the above registries and future failures to make appropriate registrations in "IPv6 Locally-Served DNS Zone" such as in {{!RFC9637}}.¶

PLEASE REMOVE THE FOLLOWING PARAGRAPH BEFORE PUBLISHING: The source for this draft is maintained on GitHub at: https://github.com/moonshiner/draft-dnsop-rfc6303-bis¶

2. Terminology

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here. DNS terminology is as described in [RFC8499].¶

3. Updates to RFC 6063

Please update {{Section 8 of @!RFC6303}} "IANA Considerations" as follows:¶

OLD:¶

{:quote}¶

This registry can be amended through "IETF Review" as per {{?RFC5226}}. As part of this review process, it should be noted that once a zone is added it is effectively added permanently; once an address range starts being configured as a local zone in systems on the Internet, it will be impossible to reverse those changes.¶

NEW:¶

{:quote}¶

This registry can be amended through "Expert Review" policy ({{Section 4.5 of !RFC8126}}). As part of this review process, it should be noted that once a zone is added it is effectively added permanently; once an address range starts being configured as a local zone in systems on the Internet, it will be impossible to reverse those changes. More guidance for Designated Experts is provided in {{guidance}} of THIS_DOCUMENT.¶

4. Changes to the IP Special-Purpose Space Registries

5. Operational Considerations

TBC.¶

6. Security Considerations

This document does not add new security risks other than those already discussed in {{RFC6303}}, {{!RFC6890}}, and {{!RFC9637}}.¶

7. IANA Considerations

Sections 6063-updates and 6890-updates include actions for IANA. These actions are not repeated here.¶

Acknowledgements

Author's Address