Live DNS lookups for devops & agent workflows.
An agent or devops workflow needs a live, sourced DNS answer — not a cached guess. Dynamic Feed runs a live DNS-over-HTTPS query for the name you specify and returns the records, signed and timestamped.
The call
Keyless over MCP, or one REST call with a free key. Every datapoint is provenance-stamped and citeable.
# Keyless — one signed call over REST:
curl -s https://dynamicfeed.ai/v1/batch -H "Content-Type: application/json" \
-d '{"calls":[{"tool":"dns_lookup","args":{"name":"github.com"}}]}'
# MCP (keyless) — point any client at https://dynamicfeed.ai/mcp, then call dns_lookup(name="github.com")Sample response
{ "name": "example.com", "type": "A", "count": 2, "answers": ["..."], "resolver_status": "NOERROR",
"source": "Cloudflare DoH", "signature": { "alg": "Ed25519", "key_id": "df-ed25519-4cb32e72f333" } }Why live data
Dynamic Feed runs a live DNS-over-HTTPS query (via Cloudflare DoH) for the name and record type you specify and returns the answers and resolver status, in a provenance envelope, signed over their exact bytes and verifiable against /.well-known/keys. This is a live resolution we perform at request time — it reflects what the resolver returned at that moment, which can vary by resolver and during propagation. It surfaces that answer, not a guarantee of global DNS state.
Use it for
- Resolve a name live, with a signed record of the answer
- A point-in-time record of a domain's DNS during an incident
- Agents / monitors that must verify DNS, not assume it
- Pairs with TLS-certificate, CVE and service-status feeds
FAQ
What's the source?
A live DNS-over-HTTPS query via Cloudflare's resolver. We name it in the provenance envelope and sign the answer.
Is it the global DNS truth?
It's what the resolver returned at that moment. DNS answers can differ by resolver and during propagation — treat it as one signed observation, not a global guarantee.
What record types?
Common types (A, AAAA, MX, TXT, CNAME, NS and more) via the type argument.