RFC 4592 - The Role of Wildcards in the Domain Name System
Network Working Group
Request for Comments: 4592
Updates: 1034, 2672
Category: Standards Track
E. Lewis
NeuStar
July 2006
Status of This Memo
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.
Contents
- 1. Introduction
- 2. Wildcard Syntax
- 3. Impact of a Wildcard Domain Name on a Response
- 4. Considerations with Special Types
- 4.1 SOA RRSet at a Wildcard Domain Name
- 4.2 NS RRSet at a Wildcard Domain Name
- 4.3 CNAME RRSet at a Wildcard Domain Name
- 4.4 DNAME RRSet at a Wildcard Domain Name
- 4.5 SRV RRSet at a Wildcard Domain Name
- 4.6 DS RRSet at a Wildcard Domain Name
- 4.7 NSEC RRSet at a Wildcard Domain Name
- 4.8 RRSIG at a Wildcard Domain Name
- 4.9 Empty Non-terminal Wildcard Domain Name
- 5. Security Considerations
- 6. References
- 7. Others Contributing to the Document
- Full Copyright Statement
- Intellectual Property
- Acknowledgement