ZeqDNS — mathematical domain resolution
Ordinary DNS is a lookup: you ask a server someone runs, and you trust its answer. ZeqDNS replaces the lookup with a computation. Every node in the lattice has a mathematical address derived from its own node secret, and to find a node you don't query a registry — you compute its address from the name. The resolver is math, so there's no authority in the middle to trust, spoof, or take offline.
Resolution is a function
A name resolves through a deterministic function of the name itself, seeded through the framework's own constants:
The domain is hashed, the first bytes become a seed, and the seed is run through the 1.287 Hz pulse and 0.777 s tick to land on an address. The same name always resolves to the same address, on every node — resolution is reproducible and needs no shared table.
Human-legible names
Raw addresses are for machines; people get .hz names. A .hz name maps a readable label (for
example alice.hz) onto the mathematical layer, so you can address a machine or node by name instead
of by its slug or numeric address — and the mapping is itself auditable state on the chain, not a
setting on a server.
curl -s https://zeqsdk.com/api/dns/resolve -d '{"domain":"api.zeq.dev"}' # name → mathematical address
curl -s https://zeqsdk.com/api/dns/lookup/ADDRESS # address → node
curl -s https://zeqsdk.com/api/dns/status
Registration (/dns/register) binds a name; the resolver does the rest by computation. Because names
and addresses both derive from fixed math, ZeqDNS holds the same properties as the rest of the
framework: deterministic, node-local, and verifiable rather than asserted.
Read next
- Mesh & self-hosting — the gossip mesh names ride on, and standing up your own node.
- Nodes and node-locality — why every node resolves a name the same way.
- ZeqID — identity derived by computation, the same idea applied to people.