Date: Sun, 05 May 2002 14:08:52 -0400 From: Eric Brunner-Williams in Portland Maine <brunner@nic-naa.net> To: Ceri Davies <setantae@submonkey.net> Cc: Johan Karlsson <k@numeri.campus.luth.se>, cvs-all@FreeBSD.ORG, brunner@nic-naa.net Subject: Re: cvs commit: doc/en_US.ISO8859-1/books/faq book.sgml Message-ID: <200205051808.g45I8qkx055023@nic-naa.net> In-Reply-To: Your message of "Sun, 05 May 2002 17:58:47 BST." <20020505165847.GA13817@submonkey.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> > Shouldn't this be 'example.com' since you made an effort to change other
> > stuff to that.
>
> Well, example.{com,net,org} are all reserved, and since this is an ISP being
> referred to, I felt that example.net was more appropriate.
Personally I wouldn't recommend any preference for an NSI property, there are
lots of countries (other than the mess of .us) which are reasonable choices,
and Donald Eastlake did suggest some conventions in RFC 2606.
2. TLDs for Testing, & Documentation Examples
There is a need for top level domain (TLD) names that can be used for
creating names which, without fear of conflicts with current or
future actual TLD names in the global DNS, can be used for private
testing of existing DNS related code, examples in documentation, DNS
related experimentation, invalid DNS names, or other similar uses.
For example, without guidance, a site might set up some local
additional unused top level domains for testing of its local DNS code
and configuration. Later, these TLDs might come into actual use on
the global Internet. As a result, local attempts to reference the
real data in these zones could be thwarted by the local test
versions. Or test or example code might be written that accesses a
TLD that is in use with the thought that the test code would only be
run in a restricted testbed net or the example never actually run.
Later, the test code could escape from the testbed or the example be
actually coded and run on the Internet. Depending on the nature of
the test or example, it might be best for it to be referencing a TLD
permanently reserved for such purposes.
To safely satisfy these needs, four domain names are reserved as
listed and described below.
.test
.example
.invalid
.localhost
".test" is recommended for use in testing of current or new DNS
related code.
".example" is recommended for use in documentation or as examples.
".invalid" is intended for use in online construction of domain
names that are sure to be invalid and which it is obvious at a
glance are invalid.
The ".localhost" TLD has traditionally been statically defined in
host DNS implementations as having an A record pointing to the
loop back IP address and is reserved for such use. Any other use
would conflict with widely deployed code which assumes this use.
3. Reserved Example Second Level Domain Names
The Internet Assigned Numbers Authority (IANA) also currently has the
following second level domain names reserved which can be used as
examples.
Eastlake & Panitz Best Current Practice [Page 2]
^L
RFC 2606 Reserved Top Level DNS Names June 1999
example.com
example.net
example.org
...
Eric
Defeat Autism Now, Maine FEAT
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200205051808.g45I8qkx055023>