The GNU Name System
The GNU Name System (GNS) is a decentralized, censorship-resistant and privacy-preserving alternative to the Domain Name System (DNS). It is the most mature part of GNUnet, its protocol is published as RFC 9498, and it is the best place to start if you are new to GNUnet.
Tip
Want to try it right away? The Quick start gets you a working zone in five commands.
What GNS gives you
- Names that nobody can take away from you.
In DNS, names are rented from a registrar under rules set by registries and ICANN, and they can be seized, blocked or redirected. In GNS, a zone is a key pair that you generate yourself. Only the holder of the private key can change the records in a zone.
- No central root.
Each user is the root of their own namespace: the names that resolve on your system are determined by your own configuration. You link to other people’s zones (delegation) under names that you choose (petnames). GNUnet ships with a small default set of zones so that common names work out of the box.
- Private lookups.
Records are encrypted and stored in GNUnet’s distributed hash table (DHT). The peers that store and route a query learn neither the name being looked up nor the answer, unless they already know both the zone and the name.
- Authentic answers.
Every record is signed with the zone key, so a resolver can verify an answer without trusting the network that delivered it.
- DNS compatibility.
GNS supports the usual DNS record types (
A,AAAA,MX,TXT, …), can serve unmodified applications through a DNS bridge, and comes with tools to import existing DNS zones.
How it works, in one paragraph
Your zone is identified by its public key, for example
000G0507HZ8M09QWA93N2YX9Y9357777C0HTPK7PA0HTKJS5GCXXPGKBWC. You add
records to it with gnunet-namestore; your peer signs and encrypts the
records you mark as public and stores them in the DHT. To resolve
www.alice.myzone, your resolver starts in your own zone myzone,
finds that the label alice delegates to Alice’s zone key, and then
fetches and decrypts the record set for www in Alice’s zone. Each step
is verified with the respective zone key. Concepts explains this in
detail.
GNS compared with DNS
DNS |
GNS |
|
|---|---|---|
Who controls a name |
registrar, registry and ultimately ICANN |
whoever holds the zone’s private key |
Root of trust |
one global root zone |
each user’s own start zones |
Globally unique names |
yes |
no: names are relative to the user (petnames) |
Query privacy |
queries are visible to resolvers and name servers |
queries and answers are hidden from the peers storing and routing them |
Record authenticity |
optional (DNSSEC) |
always (every record set is signed) |
Censorship |
names can be seized or blocked centrally |
there is no central point at which to seize a name |
The price for this is that names are not globally unique: www.alice
means whatever you decided alice refers to. The Frequently asked questions about GNS discusses
this trade-off.
Current status
GNS is the most mature component of GNUnet. The protocol is specified in RFC 9498, its C API is marked stable (see Subsystem stability), and managing your own zones and resolving names in them works well. What is still rough:
Resolving names in other people’s zones goes through the GNUnet peer-to-peer network, which is still small and has known connectivity issues. Such lookups can be slow or fail; names in your own zones always resolve locally.
Using GNS names in browsers and other ordinary applications requires some manual configuration (see Using GNS names in applications).
Exchanging zone keys via printed business cards and QR codes does not currently work (see Publishing and sharing your zone).
See What works today for the state of all GNUnet components.
In this section
Further reading
RFC 9498, the normative specification, maintained as LSD 0001
Talks and videos about GNS
Research papers in the GNUnet bibliography