RFC 6303: Locally Served DNS Zones
In plain English — editorial summary, not part of the RFC
Experience with the Domain Name System (DNS) has shown that there are a number of DNS zones that all iterative resolvers and recursive nameservers should automatically serve, unless configured otherwise. RFC 4193 specifies that this should occur for D.F.IP6.ARPA. This document extends the practice to cover the IN-ADDR.ARPA zones for RFC 1918 address space and other well-known zones with similar characteristics. This memo documents an Internet Best Current Practice.
Document record
- Document ID
- RFC6303
- Published
- July 2011
- Authors
- M. Andrews
- Status
- BEST CURRENT PRACTICE
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- BCP163
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5855Nameservers for IPv4 and IPv6 Reverse ZonesCurrent
May 2010
- RFC 6304AS112 Nameserver OperationsObsoleted
July 2011
- RFC 7534AS112 Nameserver OperationsCurrent
May 2015
- RFC 6305I'm Being Attacked by PRISONER.IANA.ORG!Current
July 2011
- RFC 6308Overview of the Internet Multicast Addressing ArchitectureCurrent
June 2011
- RFC 6312Mobile Networks Considerations for IPv6 DeploymentObsoleted
July 2011
- RFC 6313Export of Structured Data in IP Flow Information Export (IPFIX)Current
July 2011
- RFC 6291Guidelines for the Use of the "OAM" Acronym in the IETFUpdated
June 2011
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?