What is it used for?I got this definition on its importance but thats about it.

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

So what about domain name example.com?
Sorry but your title appears misleading a bit.

You seem to be missing the entire context of the quote so whatever the question is make no sense at all.

Originally Posted by chrishirst

You seem to be missing the entire context of the quote so whatever the question is make no sense at all.

Still can't get what he is talking about. It seems he wanted to share some of his thoughts with us.

Just read it in context, and NOW it makes sense.

It is from RFC2606 DNS Specifications.

It refers to the need for DNS server administrators being able to create "local" DNS names and TLDs that never go outside the confines of a LAN (Local Area Network) or a company intranet or WAN (Wide Area Network)
Such names (and IPs) should never be synchronised or propagated to the global DNS system.

EG:
I run my own DNS server with a tld of .lcl, this allows me to run a inhouse development server to test sites in a live environment.
It also means that I can have port 53 open and allow clients to use my DNS server IP externally and see their site on my test server without the risk of any third party (SEs) locating the test site because the names only exist on the one server.
Because there are no "glue" records for my system the root servers do not try to read the zones, but I can send queries out to the global system for the public zones.

Just read it in context, and NOW it makes sense.

It is from RFC2606 DNS Specifications.

It refers to the need for DNS server administrators being able to create "local" DNS names and TLDs that never go outside the confines of a LAN (Local Area Network) or a company intranet or WAN (Wide Area Network)
Such names (and IPs) should never be synchronised or propagated to the global DNS system.

EG:
I run my own DNS server with a tld of .lcl, this allows me to run a inhouse development server to test sites in a live environment.
It also means that I can have port 53 open and allow clients to use my DNS server IP externally and see their site on my test server without the risk of any third party (SEs) locating the test site because the names only exist on the one server.
Because there are no "glue" records for my system the root servers do not try to read the zones, but I can send queries out to the global system for the public zones.

OOOOhhhh...need to start checking the forums I start :-)....forgot why I asked

So what about domain name example.com?
Sorry but your title appears misleading a bit.

Sorry I don't know why I worded it that way. I mean seriously, I really don't remember :-(

Sorry I don't know why I worded it that way. I mean seriously, I really don't remember :-(

Well. Was Chris right, was not he?