DNS, DHCP & IP Address Management appliances
For Microsoft DNS & DHCP servers
For open source DNS & DHCP servers
Cloud-based visualization of analytics across DDI architecture
Manage multi-vendor cloud DNS servers centrally
RIR Declaration Management and Automation
Automated network device configuration and management
Centralized visibility over all your clouds
A single source of truth for your network automation
Why DDI is an Obvious Starting Point
DNS Threat Intelligence for proactive defense
Intelligence Insights for Threat Detection and Investigation
Adaptive DNS security for service continuity and data protection
Improve Application Access Control to prevent spread of attacks
Protect users and block DNS-based malware activity
Carrier-grade DNS DDoS attack protection
Optimize application delivery performance from the edge
for Proactive Network Security
Visibility, analytics and micro segmentation for effective Zero Trust strategy
Enable work from anywhere by controlling access, security and data privacy
Simplify management and control costs across AWS, Azure and GCP environments
Policy enforcement, risk management, and automation for simplifying compliance
Risk-free migration to reduce DDI complexity and cost
Move risk-free to improve performance, security and costs
Automate management, unify control and strengthen security of connected devices
Protect your network against all DNS attacks, data exfiltration and ransomware
Enable zero touch operations for network management and security
Improve resiliency, deployment velocity and user experience for SD-WAN projects
Integrated DNS, DHCP, IPAM services to simplify, automate and secure your network.
Simplify design, deployment and management of critical DDI services for telcos
Optimize administration and security of critical DDI services for healthcare
Simplify and automate management of critical DDI services for finance
Simplify and automate management of critical DDI services for higher education
Simplify and automate management of critical DDI services for retail
Simplify Management and Automation for Network Operations Teams
Elevate SecOps Efficiency by Simplifying Threat Response
Enable DevOps practices to deliver consistent network operations.
Open architecture for DDI integration
Technology partnerships for network security & management ecosystems
Extend security perimeters and strengthen network defenses
Submit requests for temporary licenses
Submit access requests for EfficientIP knowledge platforms
Submit membership requests for EfficientIP Community
Strengthen your network security with insights from the Forrester 2025 Study on DNS Security.
Customer-centric DDI project delivery and training
Acquire the skills needed to manage EfficientIP SOLIDserverâ„¢
Identify vulnerabilities with an assessment of your DNS traffic
Test your protection against data breaches via DNS
Dedicated representation for your organization inside EfficientIP
Explore content which helps manage and automate your network and cloud operations
Read content which strengthens protection of your network, apps, users and data
Learn how to enhance your app delivery performance to improve resilience and UX
See all your assets in one place
This enterprise-grade cloud platform allows you to improve visibility, enhance operational efficiency, and optimize network performance effortlessly.
Who we are and what we do
Meet the team of leaders guiding our global growth
Technology partnerships for network security and management ecosystems
Make your cloud projects successful with insights from the 2025 EMA Hybrid Multi-cloud Report.
Discover the benefits of the SmartPartner global channel program
Become a part of the innovation
The latest updates, release information, and global events
DNS can support AI agents without a fundamental protocol redesign, but enterprises need resilient resolvers, query visibility and enforceable policies. DNS security should complement application, identity and database controls rather than replace them.
November 17, 2026 | Written by: Paul Vixie | DNS, DNS Security
Summary
Tags
AIDNSDNS SecurityDNS over HTTPSDNSSECRPZThreat Intelligence
The DNS protocol has demonstrated its ability to accommodate successive generations of applications. AI agents are another kind of client, although their discovery patterns and automation can change the workload. An individual server still needs the capacity, headroom, and configuration to handle changing demands.
Questions about DNS proficiency produced an equally useful distinction. There is substantial expertise among specialists, coupled with a loss of basic understanding among people who can now consume DNS through services and APIs. The practical takeaway is to match knowledge to responsibility: administrators need to understand resolution, forwarding, caching and failure behavior well enough to diagnose problems even when the management interface looks healthy.
The discussion also covered organizational ownership and the difficulty of introducing DNS security when security teams wanted protection but DNS teams saw another operational responsibility. Effective policy can only result when both teams agree on enforcement, exceptions and troubleshooting.
AI agents can use existing DNS records to reach services. Discovery proposals address a more specific problem: publishing where agents are available, which protocols they support and how clients find their metadata.
Two approaches illustrate the discussion. The DNS-AID Internet-Draft uses structured names and existing Service Binding (SVCB) records. The DNS-Based Agent Naming proposal introduces AIDISCA and AIINDEX record types. Both are proposals, rather than adopted IETF standards.
One question raised was whether introducing new record types could keep pace with agent development. For operators, the immediate task is to understand the approach their applications actually implement, including publication, caching and validation requirements. Discovering an agent does not by itself establish permission to use its tools.
First and foremost, give agent workloads an approved resolution path and define the destinations they need. Establish baselines for query rates, failures and destination diversity, then investigate deviations in the context of the workload.
Next, control retry loops, concurrency and execution budgets in the agent platform as well. DNS-side limits should be tested against legitimate bursts so that protective measures do not create avoidable outages.
Finally, measure resolver latency, cache behavior and connection capacity during representative workloads. Cached answers and reused connections mean DNS query counts cannot serve as a complete count of agent actions.
A domain generation algorithm (DGA) generates candidate domain names algorithmically. Malware can use those names to locate command-and-control infrastructure. Neither an unusual name nor a high query rate establishes malicious intent by itself. Many DGA systems generate high-entropy names which don’t look like natural language words or abbreviations and may be detectable that way, but on the flip side many country-code top-level domains have wildcards which suppress negative answers (RCODE NXDOMAIN) that can otherwise help with DGA detection. This is a cat-and-mouse game having an infinite number of turns.
In response to the question about cheap, disposable domains, the discussion emphasized local protection through Response Policy Zones (RPZ), which express policies that a recursive resolver applies to DNS responses. Local enforcement gives defenders a response without waiting for a registrar or hosting provider to act.
The discussion also covered newly observed domains: names first detected by a particular observation system, which are not necessarily newly registered. Andreas described activity where queries returned NXDOMAIN before supporting infrastructure appeared. A name’s registration (WHOIS) age alone is therefore an insufficient trust signal.
The broader opportunity here is to correlate domain history, query patterns, threat intelligence and workload identity with endpoint or application evidence. DNS Guardian supports DNS traffic inspection and behavioral analysis as part of that investigation.
DNS controls can restrict resolution of database and service names. DNS Client Query Filtering supports granular policies at that layer, but schema, table and operation permissions must be enforced by the database, application or tool service.
Each agent can be given an appropriately scoped credential, allowing us to separate read access from write access and enforce authorization on every operation. For Model Context Protocol (MCP) integrations, follow the protocol’s security guidance on scope minimization and token handling.
An agent reaching an authorized endpoint must still be prevented from performing unauthorized actions there. DNS cannot repair a bypass of application or database role-based access control (RBAC).
Perhaps. DNS over HTTPS (DoH) transports DNS queries and responses over an encrypted HTTPS connection. The policy question is which resolver receives those requests.
An approved encrypted resolver can apply local policy. Applications using an external resolver can bypass that policy and remove queries from the organization’s DNS visibility. Such bypasses highlight the limits of approaches that depend entirely on client cooperation.
We must configure managed operating systems and browsers to use approved services, and combine this with appropriate endpoint and outbound connection controls. Blocking a list of known public DoH services cannot cover every private endpoint. The discussion also covered research on controlling protocols over encrypted channels. A related patent is US 11,438,309.
It shows why resolver selection has operational and governance consequences. In its October 22, 2026 announcement, Quad9 scheduled its withdrawal from serving users in France for November 24, 2026, following a court ruling requiring it to perform domain blocking.
The discussion acknowledged both national sovereignty and a provider’s ability to choose where it operates, while questioning approaches that create obvious workarounds. Andreas’s concern was whether the resolver is always the appropriate place to address harmful or unlawful content. Paul noted that motivated citizens can choose to use upstream DNS servers in other jurisdictions, or to operate their own DNS server (such as Pi-hole with Unbound).
For enterprises, the practical lesson is to understand the policies, jurisdictions and continuity arrangements attached to their chosen resolution services.
The main takeaway from the conversation is that AI makes familiar DNS responsibilities more consequential. We must each review where agents resolve names, what we can observe, how policies are enforced and who owns failures. Then we must test those controls alongside the authorization boundaries protecting the tools and data agents can access. Confidence is achievable but not without effort.
These are operational considerations, but they do not establish a single explanation for adoption. DNSSEC authenticates DNS data without encrypting it. NSEC can expose zone names, while NSEC3 introduces processing costs, and RFC 9276 recommends zero additional hashing iterations when NSEC3 is used. A forward-looking concern is that larger post-quantum signatures could increase response sizes and connection pressure as DNSSEC evolves. Test TCP reachability and capacity today: RFC 7766 already requires UDP and TCP support in general-purpose DNS implementations.
No naming design alone guarantees that a service remains reachable. Blockchain-based systems can distribute control of naming records, but their practical resilience also depends on clients, gateways, network access and the destination service. Evaluate those dependencies and how the namespace interoperates with conventional applications. Alternative namespaces are distinct from the global DNS, as illustrated by RFC 9476.
AI-assisted processing does not by itself decide whether subscription prices will fall. DNS Threat Pulse already uses AI-assisted curation and supplies intelligence in RPZ and Client Query Filtering formats. Evaluate a feed’s coverage, relevance, false positives and update timeliness when assessing its value.
Paul Vixie and Andreas Taudte discuss how DNS must evolve for agentic AI, covering encrypted resolution, visibility, security and operational readiness.
Talk to an expert
Summarize
Networks
Explore content highlighting the value EfficientIP solutions bring to your network