DNS, DHCP & IP Address Management appliances
For Microsoft DNS & DHCP servers
For open source DNS & DHCP servers
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
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
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 mgmt of critical DDI services for telcos
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
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 Protection with Smart 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
Why Using DNS Allow Lists is a No-Brainer
Who we are and what we do
Meet the team of leaders guiding our global growth
Technology partnerships for network security and management ecosystems
Discover the benefits of the SmartPartner global channel program
Become a part of the innovation
The latest updates, release information, and global events
A recursive DNS server is a caching-only DNS (domain name system) server. It is not authoritative for any domain, it obtains all of the DNS information from other DNS servers which are authoritative for the qualified name (composed of multiple domains) that was queried by the client. In the case of website name requests, the browser extracts the name of the server (FQDN) from the URL and asks the DNS for its IP address to be able to connect to it. The recursive DNS server gathers information on records obtained from authoritative DNS servers with regards to the associated IP address. The answers to queries are stored in the cache for other similar requests.
These caching-only DNS servers are required for supporting the authoritative DNS servers to handle the workload created by the enormous number of user requests. By distributing this load, recursive DNS servers make website name requests supportable, as they reduce outgoing DNS traffic and speed up name resolution.
Recursive servers are the very first servers contacted as the result of a request. If the contacted server already has a cached response for the same query (e.g. IP address) from an authoritative server, with a valid DNS TTL (time to live), it is answered directly from the cached data. But if the recursive server does not have the IP address, it starts its check through the hierarchy of authoritative DNS servers. On the other hand, Authoritative DNS servers have their top records (NS) supplied by the internet registrars where website owners have set up their site names.
An example of a caching only name server is your ISP DNS server. For example, if an end user is trying to locate www.one.org via their web browser, this query will be sent to the ISP DNS server. Since this is a caching only server, if the answer is not in its cache database with a valid TTL, it will then start the referral process to the Root (.), Top Level Domains (.org) and finally the authoritative DNS server for one.org for the specific record (www). Once an answer is obtained it will be cached in the ISP database and sent back to the end user. At ISP, the cache hit ratio is most of the time between 85% and 95%.
We use cookies to enhance your browsing experience, serve personalized content, and analyze our traffic. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site.
