metasystema.org
UpdatedBEST CURRENT PRACTICEIETF streamBCP32

RFC 2606: Reserved Top Level DNS Names

Still current, but amended. Parts of this document are changed or extended by RFC 6761. Read both.

In plain English — editorial summary, not part of the RFC

To reduce the likelihood of conflict and confusion, a few top level domain names are reserved for use in private testing, as examples in documentation, and the like. In addition, a few second level domain names reserved for use as examples are documented. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements.

Document record

Document ID
RFC2606
Published
June 1999
Authors
D. Eastlake 3rd; A. Panitz
Status
BEST CURRENT PRACTICE
Stream
IETF
Area
int
Pages
5
Also known as
BCP32
Updated by:
RFC 6761

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

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?

canonical URL: /rfc/2606-reserved-top-level-dns-names