difference between iterative and recursive dns query
DNS is the most critical infrastructure, that's publicly available for use to everybody out there. You can infact say that, its a single point of failure, that can take down the world wide web.
I have tried to explain the working of DNS in one of my post. However, its impossible to conclude the entire topic, in one or even multiple posts for that matter. So i will be posting, different topics related to DNS, separately for giving a better understanding to the reader.
Read: How Does DNS Work
In this post, we will walk through different types of queries that a client uses to get different types of information from the DNS server.
What are the different types of DNS queries?
DNS queries can be classified according the manner in which a complete request is processed. Generally queries can be classified as follows.
- recursive query
- iterative query OR Nonrecursive query
- Inverse queries
What is a recursive query?
A recursive query is a kind of query, in which the DNS server, who received your query will do all the job of fetching the answer, and giving it back to you. During this process, the DNS server might also query other DNS server's in the internet on your behalf, for the answer.
Lets understand the entire process of recursive queries by the following steps.
Suppose you want to browse www.example.com, and your resolve.conf file has got the following entry.
[root@myvm ~]# cat /etc/resolv.conf nameserver 172.16.200.30 nameserver 172.16.200.31
How does the name server select one from the given list of servers to query?
In the above case, you might have seen that our DNS server 172.16.200.30, had to select one server, from the given list of servers to query, multiple times.
For example there are 13 root servers(Well when i say 13 root servers, 13 is the number of addresses that is universal. There are Hundreds of servers at different locations in the world. These 13 root server addresses are anycasted addresses.), which root server will be queried, for an answer?
Almost all DNS server's uses an algorithm, to select one from the list, in order to distribute the load and response time.
The most Famous DNS server software BIND uses a technique called as rtt metric(Round Trip Time metric). Using this technique, the server tracks the RTT of each root server, and selects the one,with lower RTT.
What is an iterative or Non-recursive query?
Before beginning the explanation for iterative query. An important thing to note is that, all DNS server's must support iterative(non-recursive)query.
In an iterative query, the name server, will not go and fetch the complete answer for your query, but will give back a referral to other DNS server's, which might have the answer. In our previous example our DNS server 172.16.200.30, went to fetch the answer on behalf of our resolver, and provided us with the final answer.
But if our DNS server 172.16.200.30 is not a recursive name server(which means its iterative), it will give us the answer if it has in its records. Otherwise will give us the referral to the root servers(it will not query the root server's and other servers by itself.).
Now its the job of our resolver to query the root server, .COM TLD servers, and authoritative name server's, for the answer.
Lets go through the steps involved.
STEP 1: You enter www.example.com in the browser. So the operating system's resolver will send a DNS query for the A record to the DNS server 172.16.200.30 .
STEP 2: The DNS server 172.16.200.30 on receiving the query, will look through its tables(cache) to find the IP address(A record) for the domain www.example.com. But it does not have the entry.
STEP 3: Now instead of querying the root server's, our DNS server will reply us back with a referral to root servers. Now our operating system resolver, will query the root servers for the answer.
Now the rest of the steps are all the same. The only difference in iterative query is that
- if the DNS server does not have the answer, it will not query any other server for the answer, but rather it will reply with the referral to DNS root server's
- But if the DNS server has the answer, it will give back the answer(which is same in both iterative and recursive queries)
- in an iterative query, the job of finding the answer(from the given referral), lies to the local operating system resolver.
It can be clearly noted from the above figure, that in an iterative query, a DNS server queried will never go and fetch the answer for you(but will give you the answer if it already has the answer). But will give your resolver a referral to other DNS server's(root server in our case).
We will be discussing inverse queries in another post. Hope this post was helpful in understanding iterative(non-recursive) & recursive DNS queries.
- Docker Tutorial: How to Install and Use Containers
- Difference between Hypervisor Virtualization and Container Virtualization
- OpenStack Tutorial: Getting started with basics of building your own cloud
- MX Record in DNS Explained with Example Configurations
- How to Integrate AWS Cloudtrail logs in Logstash