Decentralized AI Agent Discovery via DNS-AID and RFC 8552

Why DNS-AID? Beyond Centralized Catalogs

Most AI discovery formats rely on centralized registries or GitHub scraping. DNS-AID (DNS-based Agent Identification and Discovery), governed under the Linux Foundation and IETF drafts (draft-mozleywilliams-dnsop-dnsaid), solves this by utilizing the internet's most robust directory: the Domain Name System (DNS).

How DNS-AID Works Without New Record Types

Rather than inventing proprietary DNS records, DNS-AID layers on top of standard, widely deployed RFCs:

• RFC 8552 (Scoped Underscored Names): Organizes agent records under _{name}._{protocol}._agents.{domain}.
• RFC 9460 (SVCB Service Binding): Maps the agent name directly to target ports, ALPN protocols, and URI paths.
• DNSSEC & DANE: Provides unforgeable cryptographic authenticity from the DNS root down to individual agents.

Example Cloudflare DNS Configuration

; Map MCP agent endpoint
_chatbot._mcp._agents.example.com.   IN  SVCB  1 chatbot.example.com. (
                                          alpn="h2"
                                          port=443
                                          key65300="path=/mcp"
                                      )

; Metadata and version record
_chatbot._meta._agents.example.com.  IN  TXT   "v=aid1;ver=1.0.0;name=com.example/chatbot"

ActionGuard automatically generates these records from any inspected endpoint or actionguard.json manifest.