A hot public cache key can reduce many client reads to roughly one authoritative miss per cache instance per TTL. Private reads use TTL 0.
Leverage the DNS infrastructure you already have.
Public answers can be cached by recursive resolvers. Three unicast regions serve uncached reads; resolver selection does not guarantee the nearest node.
Public cache hits avoid application cold starts and connection setup. Private token-authorized answers intentionally use DNS TTL 0.
DNSSEC protects answer integrity, while DoH and DoT encrypt queries in transit. Encrypt sensitive values client-side before upload.
If your language can make DNS queries, it can use ResolveDB. No SDK required.
The UQRP format encodes operations, parameters, and namespaces directly in DNS labels.
Create one namespace and record, then query it with standard DNS tools or the HTTPS API.
Query data using standard DNS tools.
Use the dashboard or API to store key-value data under your namespace.
Make standard DNS TXT queries using dig, nslookup, or any DNS library.
Receive structured UQRP responses. Public answers are cacheable; private token-authorized answers use DNS TTL 0.
From AI agents to factory floors, see how teams use DNS as their data layer.