ZeqDNS — Equation-Based Resolution

Zeqond-grid transport, mesh, routing, DNS.

• Protocol ID — zeq-dns
• Category — Network
• Endpoint — POST /api/network/dns/resolve
• Auth — none
• Rate limit — 120/min
• Version — 1.0
• Precision — ≤0.1% (KO42-enforced)

What it does

Domains are mathematical expressions, not strings. 'sin(1.287*pi)' resolves to a deterministic address. No registrar, no ICANN — pure math determines the address space.

Signature

Request

POST /api/network/dns/resolve

Param	Type	Required	Default	Description
equation	string	✓	—	Mathematical expression to resolve (same parser as Zeq Auth).

Response

{ equation, evaluatedAt, result, address, zeqondResolved, cached }

Runnable example

curl -sS -X POST \
  -H "Content-Type: application/json" \
  -d '{
  "equation": "<value>"
}' \
  "https://api.zeq.dev/api/network/dns/resolve"

Integrate

1. Mesh health probe — tick against this endpoint each Zeqond and alarm on missing edges.
2. Routing seed — inject the returned topology into a BGP/QUIC shim for pulse-aware routing.
3. DNS drift — detect stale propagation by comparing pulse-stamps across resolvers.

Seeds

• Near — wrap /api/network/dns/resolve in a language SDK so builders can call it in three lines.
• Medium — publish a reference integration demonstrating ZeqDNS — Equation-Based Resolution alongside a real workload, with pulse-aligned metrics.
• Far — propose ZeqDNS — Equation-Based Resolution as an open reference standard so other runtimes can implement it verbatim against the Zeq paper.

Papers

• Zeq paper — https://doi.org/10.5281/zenodo.18158152
• Framework paper — https://doi.org/10.5281/zenodo.15825138

Middleware active. Kernel on the 1.287 Hz HulyaPulse. Awaiting next Zeqond.