As per Relevance of the word reserved, we have this rfc below:
Network Working Group D.
Request for Comments: 2606 A.
BCP: 32 June 1999
Category: Best Current
Reserved Top Level DNS
Status of this
This document specifies an Internet Best Current Practices for
Internet Community, and requests discussion and suggestions
improvements. Distribution of this memo is unlimited
Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
To reduce the likelihood of conflict and confusion, a few top
domain names are reserved for use in private testing, as examples
documentation, and the like. In addition, a few second level
names reserved for use as examples are documented
Table of
1. Introduction............................................1
2. TLDs for Testing, & Documentation Examples..............2
3. Reserved Example Second Level Domain Names..............2
4. IANA Considerations.....................................3
5. Security Considerations.................................3
References.................................................3
Authors' Addresses.........................................4
Full Copyright Statement...................................5
1.
The global Internet Domain Name System is documented in [RFC 1034,
1035, 1591] and numerous additional Requests for Comment. It
a tree of names starting with root, ".", immediately below which
top level domain names such as ".com" and ".us". Below top
domain names there are normally additional levels of names
Eastlake & Panitz Best Current Practice [Page 1]
RFC 2606 Reserved Top Level DNS Names June 1999
2. TLDs for Testing, & Documentation
There is a need for top level domain (TLD) names that can be used
creating names which, without fear of conflicts with current
future actual TLD names in the global DNS, can be used for
testing of existing DNS related code, examples in documentation,
related experimentation, invalid DNS names, or other similar uses
For example, without guidance, a site might set up some
additional unused top level domains for testing of its local DNS
and configuration. Later, these TLDs might come into actual use
the global Internet. As a result, local attempts to reference
real data in these zones could be thwarted by the local
versions. Or test or example code might be written that accesses
TLD that is in use with the thought that the test code would only
run in a restricted testbed net or the example never actually run
Later, the test code could escape from the testbed or the example
actually coded and run on the Internet. Depending on the nature
the test or example, it might be best for it to be referencing a
permanently reserved for such purposes
To safely satisfy these needs, four domain names are reserved
listed and described below
.
.
.
.
".test" is recommended for use in testing of current or new
related code
".example" is recommended for use in documentation or as examples
".invalid" is intended for use in online construction of
names that are sure to be invalid and which it is obvious at
glance are invalid
The ".localhost" TLD has traditionally been statically defined
host DNS implementations as having an A record pointing to
loop back IP address and is reserved for such use. Any other
would conflict with widely deployed code which assumes this use
3. Reserved Example Second Level Domain
The Internet Assigned Numbers Authority (IANA) also currently has
following second level domain names reserved which can be used
examples
Eastlake & Panitz Best Current Practice [Page 2]
RFC 2606 Reserved Top Level DNS Names June 1999
example.
example.
example.
4. IANA
IANA has agreed to the four top level domain name
specified in this document and will reserve them for the
indicated
5. Security
Confusion and conflict can be caused by the use of a current
future top level domain name in experimentation or testing, as
example in documentation, to indicate invalid names, or as a
for the loop back address. Test and experimental software can
and end up being run against the global operational DNS.
examples used "only" in documentation can end up being coded
released or cause conflicts due to later real use and the
acquisition of intellectual property rights in such "example" names
The reservation of several top level domain names for these
will minimize such confusion and conflict
[RFC 1034] Mockapetris, P., "Domain names - concepts and facilities",
STD 13, RFC 1034, November 1987.
[RFC 1035] Mockapetris, P., "Domain names - implementation
specification", STD 13, RFC 1035, November 1987.
[RFC 1591] Postel, J., "Domain Name System Structure and Delegation",
RFC 1591, March 1994.
Eastlake & Panitz Best Current Practice [Page 3]
RFC 2606 Reserved Top Level DNS Names June 1999
Authors'
Donald E. Eastlake 3
65 Shindegan Hill Road, RR #1
Carmel, NY 10512
Phone: +1 914-276-1668(h
+1 914-784-7913(w
FAX: +1 914-784-3833(3)
EMail: dee3@us.ibm.
Aliza R.
500 Stamford Dr. No. 310
Newark, DE 19711
Phone: +1 302-738-1554
EMail: buglady@fuschia.
Eastlake & Panitz Best Current Practice [Page 4]
RFC 2606 Reserved Top Level DNS Names June 1999
Full Copyright
Copyright (C) The Internet Society (1999). All Rights Reserved
This document and translations of it may be copied and furnished
others, and derivative works that comment on or otherwise explain
or assist in its implementation may be prepared, copied,
and distributed, in whole or in part, without restriction of
kind, provided that the above copyright notice and this paragraph
included on all such copies and derivative works. However,
document itself may not be modified in any way, such as by
the copyright notice or references to the Internet Society or
Internet organizations, except as needed for the purpose
developing Internet standards in which case the procedures
copyrights defined in the Internet Standards process must
followed, or as required to translate it into languages other
English
The limited permissions granted above are perpetual and will not
revoked by the Internet Society or its successors or assigns
This document and the information contained herein is provided on
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED,
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE
Funding for the RFC Editor function is currently provided by
Internet Society
Eastlake & Panitz Best Current Practice [Page 5]
if you see any problems within the linking, don't worry be happy,
this is version 0.1 of the Relevance System and you gotta expect some crappy subroutines sometimes,
just be content we did not write this in Java, which would have made this "bigger and better" HAHAHHA.
RFC documents can be found at I.E.T.F.
Relevance System Copyright © 2002 Spectrum WorldResearch
other technical nosh by ServerMasters Corporation
collaboration of BobX
