RFC - 4592
The Role of Wildcards in the Domain Name System
| Original: | ftp://ftp.isi.edu/in-notes/rfc4592.txt |
|---|---|
| Authors: | E. Lewis [NeuStar] |
| Date: | July 2006 |
| Category: | Proposed Standard |
| Updates: | |
|---|---|
| RFC-2672prop | Non-Terminal DNS Name Redirection (Updated by RFC-4592prop) |
| RFC-1034std13 [STD 13] |
Domain names - concepts and facilities (Updated by RFC-1876exp, RFC-1348, RFC-4033prop, RFC-4035prop, RFC-4034prop, RFC-2308prop, RFC-2065, RFC-2181prop, RFC-2535, RFC-4343prop, RFC-1982prop, RFC-4592prop, RFC-1101, RFC-1183exp) |
| Referred by: | 0 RFC |
| Refers to: | 12 RFC |
Status
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (2006).
Abstract
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.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry