Kind of. The DNS root has root nameservers, which have NS records, so you could actually do a query like this:
falcon@akira ~ $ dig in ns .
; <<>> DiG 9.8.0 <<>> in ns .
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 31632
;; flags: qr rd ra; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 0
;; QUESTION SECTION:
;. IN NS
;; ANSWER SECTION:
. 21026 IN NS g.root-servers.net.
. 21026 IN NS k.root-servers.net.
. 21026 IN NS c.root-servers.net.
. 21026 IN NS b.root-servers.net.
. 21026 IN NS d.root-servers.net.
. 21026 IN NS f.root-servers.net.
. 21026 IN NS m.root-servers.net.
. 21026 IN NS h.root-servers.net.
. 21026 IN NS a.root-servers.net.
. 21026 IN NS j.root-servers.net.
. 21026 IN NS l.root-servers.net.
. 21026 IN NS i.root-servers.net.
. 21026 IN NS e.root-servers.net.
;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sat Oct 20 12:15:07 2012
;; MSG SIZE rcvd: 228
This data normally comes from what are called glue records, stored in a file on individual DNS servers; when the DNS server goes to resolve a name; this is also how a DNS server gets the address of one to query it.
Those root servers have information on where to find nameservers for the various TLDs, which in turn have information on where to find nameservers for individual domains.
There is not, and likely will never be, an A, AAAA, MX, or other such record for the DNS root
., so querying on that data will of course never succeed. Likewise, though there are name servers (the root servers above) that are authoritative for
., it does not refer to an actual host.
For more on that topic, have a look at how recursive DNS name resolution works. It is quite simple: essentially, a DNS server starts at the root, queries one of the root servers, asks for the record it wants, and gets a referral with an NS record instead. It keeps doing this until it finds the authoritative server for the name it is querying, which is actually able to answer. This process is expensive, so many nameservers cache this response for the TTL (in this example, 21026 seconds).