agent-ready-dns-aid — Claude Code skill: DNS-AID setup
The agent-ready-dns-aid skill guides DNS-AID records that let agents locate endpoints through DNS. Use it when publishing SVCB or HTTPS records under _agents.
Apache-2.0 ★ 141 updated 2026-10-29
npx skills add fabricioctelles/skills --skill agent-ready-dns-aid -a claude-codeWhat agent-ready-dns-aid does
The skill covers DNS for AI Discovery records in the _agents namespace, such as _a2a._agents.example.com. It uses ServiceMode SVCB, or HTTPS for HTTPS endpoints, with alpn and connection settings. Experimental custom parameters use numeric keyNNNNN names until they are registered.
Discovery zones must carry DNSSEC signatures so validating resolvers can authenticate the returned data. The checker queries DNS over HTTPS through https://cloudflare-dns.com/dns-query by default and falls back to https://dns.google/resolve when the resolver itself fails. Library users can set ScanOptions.dohResolverUrl; doing so disables that fallback.
Run a check through https://isitagentready.com/api/scan with the site URL in the request. The expected result is "pass" at checks.discoverability.dnsAid.status. Without DNSSEC, the zone misses the authentication requirement.
What it helps with
- publish an endpoint for agent discovery through DNS
- create an SVCB record under
_agents - set
alpn, the port, and connection parameters - sign the discovery zone with DNSSEC
- check DNS-AID through DNS-over-HTTPS
Example prompts for the agent
- Set up DNS-AID for my endpoint under
_agents, includingalpnand the connection parameters. - Write an SVCB record for this A2A endpoint and check it through
https://isitagentready.com/api/scan. - Verify the DNS zone uses DNSSEC and that
checks.discoverability.dnsAid.statusis"pass".
How to install agent-ready-dns-aid
1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill agent-ready-dns-aid -a claude-code2Manually: put the files in place
~/.claude/skills/dns-aid/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/dns-aid/
1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill agent-ready-dns-aid -a codex2Manually: put the files in place
.agents/skills/dns-aid/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill agent-ready-dns-aid -a cursor2Manually: put the files in place
.cursor/skills/dns-aid/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install fabricioctelles/skills skills/agent-ready-cloudflare/dns-aid2Manually: put the files in place
.github/skills/dns-aid/SKILL.md1Skills CLI (Vercel)
npx skills add fabricioctelles/skills --skill agent-ready-dns-aid -a gemini-cli2Platform CLI
gemini skills install https://github.com/fabricioctelles/skills --path skills/agent-ready-cloudflare/dns-aidManually: put the files in place
.devin/skills/dns-aid/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about agent-ready-dns-aid
How do I install agent-ready-dns-aid in Claude Code?
Run npx skills add fabricioctelles/skills --skill dns-aid -a claude-code, then use the skill at ~/.claude/skills/dns-aid/SKILL.md.
What does agent-ready-dns-aid do?
It guides DNS-AID discovery records under _agents, allowing agents to find endpoints through DNS. The skill covers SVCB and HTTPS records, alpn, connection settings, and DNS-over-HTTPS checks.
Why does a DNS-AID zone need DNSSEC?
DNSSEC authenticates discovery data, so validating resolvers can return verified DNS responses.
Source text
SKILL.md · Apache-2.0
---
name: agent-ready-dns-aid
description: >
Sub-skill: Implement DNS-AID records so agents discover endpoints through DNS.
Use SVCB/HTTPS records under _agents namespace with alpn and connection parameters.
---
# Implement DNS for AI Discovery (DNS-AID)
Publish DNS for AI Discovery (DNS-AID) records so agents can discover your agent endpoints through DNS.
## Requirements
- Publish DNS for AI Discovery (DNS-AID) records under your domain's `_agents` namespace, such as `_index._agents.example.com` or `_a2a._agents.example.com`
- Use ServiceMode `SVCB` records, or `HTTPS` records for HTTPS endpoints, with `alpn` and endpoint connection parameters
- Use numeric `keyNNNNN` SvcParamKey names for experimental DNS for AI Discovery (DNS-AID) custom parameters until they are registered
- Sign public DNS for AI Discovery (DNS-AID) discovery zones with DNSSEC so validating resolvers return authenticated data
## Example
```dns
_a2a._agents.example.com. 3600 IN SVCB 1 agent.example.com. alpn="a2a" port=443 mandatory=alpn,port
```
## Validate
The scanner validates DNS for AI Discovery (DNS-AID) via DNS-over-HTTPS. By default, the scanner uses Cloudflare's `https://cloudflare-dns.com/dns-query` with automatic fallback to `https://dns.google/resolve` on resolver-level failures. Library callers can override the resolver with `ScanOptions.dohResolverUrl` (disables fallback).
```http
POST https://isitagentready.com/api/scan
Content-Type: application/json
{"url": "https://YOUR-SITE.com"}
```
Check that `checks.discoverability.dnsAid.status` is `"pass"`.
## References
- [draft-mozleywilliams-dnsop-dnsaid](https://datatracker.ietf.org/doc/draft-mozleywilliams-dnsop-dnsaid/)
- [RFC 9460 — SVCB and HTTPS Resource Records](https://www.rfc-editor.org/info/rfc9460)
© fabricioctelles · Apache-2.0 · fabricioctelles/skills