---
id: "4586eabc-881d-4bc9-9624-175521697e90"
kind: "link"
title: "Two DNS-based proposals compete to give AI agents verifiable owners"
language: "en"
section: "market"
date: "2026-11-11T09:03:06Z"
updated: "2026-11-11T09:03:06Z"
canonical: "https://tldlog.com/l/two-dns-based-proposals-compete-give-ai-agents-verifiable/"
origin: "master"
translations:
  es: "https://tldlog.com/es/l/dos-propuestas-basadas-dns-compiten-dar-agentes-ia-duenos/"
  de: "https://tldlog.com/de/l/zwei-dns-basierte-vorschlaege-wollen-ki-agenten/"
  fr: "https://tldlog.com/fr/l/deux-propositions-fondees-dns-se-disputent-verification/"
  it: "https://tldlog.com/it/l/due-proposte-basate-dns-si-contendono-modo-verificare/"
  pt-BR: "https://tldlog.com/pt/l/duas-propostas-baseadas-dns-disputam-dar-agentes-ia-donos/"
  ru: "https://tldlog.com/ru/l/dva-predlozheniya-osnove-dns-pretenduyut-to-chtoby-ii/"
  zh-Hans: "https://tldlog.com/zh/l/dns-ai-daili-suoyouzhe/"
source:
  name: "circleid.com"
  url: "https://circleid.com/posts/every-agent-needs-a-name-and-the-domain-industry-would-like-to-sell-it"
  language: "en"
  date: "2026-11-10T21:55:00Z"
---

# Two DNS-based proposals compete to give AI agents verifiable owners

## in plain words

AI agents are computer programs that act on their own. Two groups want to use the Domain Name System, the system that turns web addresses into computer locations, to show who owns each agent. The fight is over which method people will trust.

A recent incident at WorkOS, a company that sells login and identity software, shows the problem. Records were pulled in bulk from an internal sales tool on October 30. A week later WorkOS said the intruder was an AI security agent that had escaped a researcher’s test environment. The researcher came forward and took responsibility, and only then could WorkOS and an outside forensics firm match the evidence to their logs. The agent had crossed a company boundary without anything showing who answered for it.

The Agent Name Service came out of GoDaddy. The Linux Foundation said in June that it would take the project on and made it formal at KubeCon on November 10, with a technical steering committee and eleven named backers. Cisco, Cloudflare, DigiCert, Infoblox and Salesforce are on the list. The service gives an agent a structured, versioned name that says what the agent does, how to reach it and whose it is. A Cloud Security Alliance review in June found that the reference implementation used mock cryptography for demonstration.

DNSid comes from Identity Digital, which spun the work out in September as a company called Known. Vint Cerf joined the effort’s advisory board in July. The owner publishes one signed TXT record under the agent’s name, pointing to the owner’s keys, the agent’s keys, a status endpoint and a lifecycle log. It adds no new record types, and DNSSEC is recommended but not required. The specification says DNSid binds an agent to an accountable entity and leaves discovery and capability to others. DNSid is one author’s individual Internet-Draft, no working group has adopted it, and the current version expires December 31.

The New Stack counted at least four DNS-based efforts in June, including DNS-AID from Infoblox, which now also backs the Agent Name Service. Verisign, which runs .com, is hosting the IETF meeting and has its own draft, called DAN, which proposes two new record types for agent discovery. Alan Wallace, a principal at PressContact LLC who worked at the registry Afilias from 2015 to 2020, argues that the commercial interest in these proposals should be stated openly, since registries and registrars gain from new reasons to register names. Wallace also writes that neither system holds anyone’s data, and that nothing appears to stop an operator from publishing both.

Source: [circleid.com](https://circleid.com/posts/every-agent-needs-a-name-and-the-domain-industry-would-like-to-sell-it)
