DNS-Native AI Agent Naming: How Domain Names Can Identify Autonomous Agents
AI agents need stable names, trusted endpoints, and a way to prove which organization controls them. A July 2026 Internet-Draft proposed DNS-native naming and resolution for AI agents using fully qualified domain names as stable agent identifiers.
The concept builds on infrastructure the internet already uses: domain ownership, DNS delegation, DNSSEC, service records, and HTTPS.
Why AI Agents Need Stable Names
An agent may move between cloud regions, rotate IP addresses, upgrade protocols, or use multiple endpoints. Hardcoded URLs create operational problems when infrastructure changes.
A domain-based identifier can remain stable while DNS directs clients to the current service.
Example Agent Identifier
travel-agent.example.comThe organization controlling example.com can publish records describing where the agent is available and which protocols it supports.
What DNS-Native Resolution Can Publish
- Agent endpoint hostname
- Supported protocol
- Protocol version
- Service priority
- Alternative endpoints
- Integrity metadata
- Fallback HTTPS resources
Why DNSSEC Matters
Without DNSSEC, an attacker who can manipulate DNS responses may redirect an agent client to a false endpoint. DNSSEC allows validating clients to verify that signed DNS records came from the authoritative zone and were not altered.
A fail-closed design can reject an endpoint when critical signed records validate as bogus.
DNS Naming Is Not the Same as Trusting the Agent
A correctly signed DNS record proves control of the DNS data, not that the agent is safe, accurate, honest, or authorized for every task.
Agent consumers still need:
- Organizational policy
- Reputation checks
- Code or model attestation
- Permission limits
- Audit logs
- Human approval for high-risk actions
Potential Benefits
- Vendor-neutral agent identity
- Portable endpoints
- Compatibility with existing DNS infrastructure
- Decentralized organizational control
- Cacheable resolution
- DNSSEC-based integrity
Operational Challenges
- DNSSEC deployment complexity
- Record-format standardization
- Protocol-version negotiation
- Key rotation
- Private and split-horizon DNS
- Agent revocation
- Prompt-injection risk from discovered metadata
How Organizations Can Prepare
- Maintain strong control of registrar and DNS accounts.
- Enable MFA and role-based access.
- Deploy DNSSEC where operationally appropriate.
- Use short but reasonable TTLs for agent endpoints.
- Separate production and test agent namespaces.
- Monitor DNS changes and certificate issuance.
- Document agent ownership and lifecycle.
Frequently Asked Questions
Is DNS-native AI agent naming already a final standard?
No. Current documents are Internet-Drafts and may change.
Can an agent use a normal subdomain?
Yes. The concept uses normal fully qualified domain names combined with service and integrity metadata.
Does DNSSEC guarantee the agent is trustworthy?
No. It authenticates DNS data, not agent behavior.
Conclusion
DNS-native naming could give AI agents stable, decentralized identities anchored in domains that organizations already control. Its success will depend on secure DNS operations, DNSSEC, endpoint verification, and strong agent-governance policies.