El Sistema de Nombres GNU
A decentralized, censorship-resistant and privacy-preserving alternative to DNS, specified in RFC 9498. GNS is the most mature part of GNUnet and the best place to start.
Documentación
El Sistema de Nombres de Dominio hoy permite ataques a la ampliación de tráfico, censura (p.e. China), vigilancia masiva (MORECOWBELL) y guerra cibernética ofensiva (QUANTUMDNS).
Lastimosamente, soluciones rápidas como DoT, DoH, DNSSEC, DPRIVE, y similares no lo arreglarán. Es por esto que construimos el Sistema de Nombres GNU (GNS), un sistema de nombres seguro y descentralizado construido sobre GNUnet.
Características
- Names you own. A zone is a key pair you create yourself. Only the holder of the private key can change its records; there is no registrar that could seize or censor it.
- No central root. Every user is the root of their own namespace and links to other people's zones under names of their choice.
- Private lookups. Records are encrypted, and the peers that store and route a query learn neither the name nor the answer.
- Authentic answers. Every record is signed with the zone key.
- DNS compatibility. GNS supports the usual DNS record types, can serve unmodified applications, and can import existing DNS zones.
Try it
After installing GNUnet, start your peer, create a zone, add a record and resolve it:
$ gnunet-arm -s $ gnunet-identity -C myzone $ gnunet-namestore -z myzone -a -n www -t A -V 192.0.2.1 -e 1d $ gnunet-gns -u www.myzone
To make a friend's zone available under the name alice, add their zone key as a delegation:
$ gnunet-namestore -z myzone -a -n alice -t EDKEY -V ALICES-ZONE-KEY -e 1d $ gnunet-gns -u www.alice.myzone
The quick start in the handbook walks you through these steps.
GNS compared with DNS
| DNS | GNS | |
|---|---|---|
| Who controls a name | registrar, registry, ICANN | the holder of the zone 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) |
| pretty Easy privacy | queries visible to resolvers and servers | queries hidden from the network |
| Signed records | optional (DNSSEC) | always |
Use it every day
- Make GNS names work in your browser and other applications with the DNS2GNS bridge.
- Register a name for your zone under
.pin.gns.altat fcfs.gnunet.org, so that every GNUnet user can resolve it. - Mirror an existing DNS zone into GNS with the migration tools.
Status
The protocol is published as RFC 9498 and the API is stable. Managing your own zones and resolving names in them works well. Lookups in other people's zones go through the GNUnet network, which is still small, and can therefore be slow. See what works today.
Recursos
- The GNS section of the handbook, including frequently asked questions.
- The specification, RFC 9498, maintained as LSD 0001, which can be used to implement resolvers for GNS.
- Videos giving an overview of GNS and the motivations behind it.
- En la bibliografía pueden encontrarse nuestros documentos técnicos.