DNS (Domain Name Server) Address Resolution Explained

DNS (Domain Name Server) Address Resolution Explained

In the realm of domain name system (DNS) resolution, two primary methods are used to translate human-readable domain names into IP addresses: recursive and iterative resolution.

Recursive Resolution

Recursive resolution is a process where a recursive DNS server takes full responsibility for resolving a domain name query. It queries multiple DNS servers on behalf of the client, starting from the root servers, until it finds the authoritative server that holds the IP address for the requested domain. The client sends one query to the recursive DNS server, which then responds with the full answer [1][3][5]. This method centralizes query processing and caching in the recursive DNS server, simplifying the client's role and often reducing latency and client load [1][3]. Recursive servers heavily use caching to store DNS answers temporarily, improving response time and lowering overall system load [1][3]. Additionally, recursive DNS servers can implement security measures like DNSSEC validation, query filtering, and rate limiting, providing enhanced security benefits to clients [1].

Iterative Resolution

In contrast, iterative resolution involves the DNS client or resolver querying multiple DNS servers step-by-step. Each server responds with either the answer or a referral to another DNS server, which the client must then query next. The client manages each query iteration [1][5]. This method distributes query handling to the client, potentially reducing server load but increasing complexity and latency at the client side. In iterative resolution, caching is primarily done by DNS servers themselves; the client may cache the last-known referral or result but typically relies on server caching along the path [1].

Comparing the Two Methods

Recursive resolution centralizes load on the recursive server because it performs multiple lookups per client query, placing more processing and network load on the recursive server [1][3]. On the other hand, iterative resolution spreads the load more evenly as the client performs most of the querying, reducing the burden on individual DNS servers and recursive resolvers [1].

Recursive resolution can be faster for the client because it only waits for one response from the recursive server. If the recursive server has cached answers, it returns immediately [3][5]. Iterative resolution often takes longer for the client since it must wait for multiple sequential server responses and manage forwarding queries itself.

Address resolution can occasionally fail due to various issues such as DNS Server Unavailability, DNS Cache Poisoning, or Incorrect DNS Configuration. In iterative resolution, the cache hit rate is lower since referrals are returned instead of mappings. Each server that does not know the mapping sends the IP Address of the next server to the one requested it. This makes iterative resolution more susceptible to errors and potential manipulation, as each server in the chain may potentially modify the response.

In summary, recursive resolution offers caching efficiencies and user simplicity, while iterative resolution distributes query handling to the client. Recursive resolution is widely used by ISPs and public DNS resolvers due to its caching benefits, while iterative resolution is primarily used in specific scenarios where caching is not a priority or where the client has the capability to manage multiple queries.

[1] - "DNS and BIND" by Paul Albitz and Cricket Liu [3] - "DNS and BIND" by Daniel J. Strohl [5] - "DNS for the Practical Networking Professional" by Paul Vixie and David Ullmer

A trie data structure could be used in the field of data-and-cloud-computing to efficiently store DNS records for recursive resolution, improving the speed and reduction of query processing traffic within the network.

The integration of advanced technology like network sandboxing in iterative resolution could enhance security by isolating and analyzing malicious DNS queries, mitigating potential risks of DNS Server Unavailability, DNS Cache Poisoning, or Incorrect DNS Configuration.

Read also: