metasystema.org
CurrentPROPOSED STANDARDIETF stream

RFC 4592: The Role of Wildcards in the Domain Name System

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

This is an update to the wildcard definition of RFC 1034. The interaction with wildcards and CNAME is changed, an error condition is removed, and the words defining some concepts central to wildcards are changed. The overall goal is not to change wildcards, but to refine the definition of RFC 1034. [STANDARDS-TRACK]

Document record

Document ID
RFC4592
Published
July 2006
Authors
E. Lewis
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
20
Also known as
—
Updates:
RFC 1034, RFC 2672

Topics

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/4592-the-role-of-wildcards-in-the-domain-name-system