Home / Blogs

Where Did the .Root Top-Level Domain Come From?

It was pointed out to me the other day that the ICANN/NTIA/Verisign root zone file contains a previously undiscussed top level domain.

The contents of this TLD suggest that it was created by Verisign, the company that actually constructs the root zone file used by the dominant set of root servers. (The same zone file is also used by at least one of the competing root systems.)

That TLD is .root. It’s existence is as real as any other TLD such as .com or .org.

Unlike most TLDs, .root TLD is not delegated to a second tier or servers. Instead it is handled directly by the root servers themselves.

.root contains exactly one name: vrsn-end-of-zone-marker-dummy-record.root.

That name is associated with exactly one resource record: a TXT record containing the single word “plenus”, a Latin word meaning “full” or “complete”.

You can check this for yourself. Try running the following Unix/Linux/BSD command:

dig vrsn-end-of-zone-marker-dummy-record.root. any @a.root-servers.net

You’ll get an error-free, authoritative response that looks something like:

; <<>> DiG 9.2.2-P3 <<
>> vrsn-end-of-zone-marker-dummy-record.root. any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 16573
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 13

;vrsn-end-of-zone-marker-dummy-record.root. IN ANY

vrsn-end-of-zone-marker-dummy-record.root. 172800 IN TXT "plenus"

... [the remaining part of response is elided] ...

You can confirm this by inspecting a copy of the root zone itself.

Where did this TLD come from? What purpose, if any, does it serve? Who authorized it?

This article originally published in the CaveBear Weblog.

By Karl Auerbach, Chief Technical Officer at InterWorking Labs

Filed Under


Comment Title:

  Notify me of follow-up comments

We encourage you to post comments and engage in discussions that advance this post through relevant opinion, anecdotes, links and data. If you see a comment that you believe is irrelevant or inappropriate, you can report it using the link at the end of each comment. Views expressed in the comments do not represent those of CircleID. For more information on our comment policy, see Codes of Conduct.

CircleID Newsletter The Weekly Wrap

More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Co-designer of the TCP/IP Protocols & the Architecture of the Internet




Sponsored byDNIB.com

Brand Protection

Sponsored byCSC


Sponsored byVerisign

Domain Names

Sponsored byVerisign

New TLDs

Sponsored byRadix

IPv4 Markets

Sponsored byIPv4.Global

Threat Intelligence

Sponsored byWhoisXML API