RFC 8501: Reverse DNS in IPv6 for Internet Service Providers
In plain English — editorial summary, not part of the RFC
In IPv4, Internet Service Providers (ISPs) commonly provide IN-ADDR.ARPA information for their customers by prepopulating the zone with one PTR record for every available address. This practice does not scale in IPv6. This document analyzes different approaches and considerations for ISPs in managing the IP6.ARPA zone.
Document record
- Document ID
- RFC8501
- Published
- November 2018
- Authors
- L. Howard
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8475Using Conditional Router Advertisements for Enterprise MultihomingCurrent
October 2018
- RFC 8683Additional Deployment Guidelines for NAT64/464XLAT in Operator and Enterprise NetworksCurrent
November 2019
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 8161Benchmarking the Neighbor Discovery ProtocolCurrent
May 2017
- RFC 8994An Autonomic Control Plane (ACP)Current
May 2021
- RFC 7934Host Address Availability RecommendationsCurrent
July 2016
- RFC 9096Improving the Reaction of Customer Edge Routers to IPv6 Renumbering EventsCurrent
August 2021
- RFC 9099Operational Security Considerations for IPv6 NetworksCurrent
August 2021
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?