April 16, 2024 By Isaac Onigman 2 min read

The dig command is a powerful tool for troubleshooting queries and responses received from the Domain Name Service (DNS). It is installed by default on many operating systems, including Linux® and Mac OS X. It can be installed on Microsoft Windows as part of Cygwin. 

One of the many things dig can do is to perform recursive DNS resolution and display all of the steps that it took in your terminal. This is extremely useful for understanding not only how the DNS works, but for determining if there is an issue somewhere within the resolution chain that cause resolution failures for your zones or domains. 

First, let’s briefly review how a query recursive receives a response in a typical recursive DNS resolution scenario: 

  1. You as the DNS client (or stub resolver) query your recursive resolver for www.example.com. 
  2. Your recursive resolver queries the root nameserver for NS records for “com.” 
  3. The root nameserver refers your recursive resolver to the .com Top-Level Domain (TLD) authoritative nameserver. 
  4. Your recursive resolver queries the .com TLD authoritative server for NS records of “example.com.” 
  5. The .com TLD authoritative nameserver refers your recursive server to the authoritative servers for example.com. 
  6. Your recursive resolver queries the authoritative nameservers for example.com for the A record for “www.example.com” and receives 1.2.3.4 as the answer. 
  7. Your recursive resolver caches the answer for the duration of the time-to-live (TTL) specified on the record and returns it to you.

The above process basically looks like this:

Step 1

Step 2

Step 3

Step 4

Step 5

This process occurs every time you type a URL into your web browser or fire up your email client. This illustrates why DNS answer speed and accuracy are so important: if the answer is inaccurate, you may need to repeat this process several times; and if the speed with which you receive an answer is slow, then it will make everything you do online seem to take longer than it should.  

Driving both DNS answer speed and accuracy is at the core of the IBM® NS1 Connect® value proposition.   

Learn more at IBM NS1 Connect
Was this article helpful?
YesNo

More from Automation

Using full stack automation to drive app-centric networking with IBM Rapid Network Automation

3 min read - Today, we’re announcing the general availability of IBM® Rapid Network Automation—the first solution that stems from our Pliant acquisition in March. IBM Rapid Network Automation is an advanced API-driven tool that is designed to automate, integrate and connect infrastructure across a hybrid cloud environment. Using a low-code approach and transforming API code into deployment-ready action blocks, IBM Rapid Network Automation is equipped with thousands of out-of-the-box integrations that help facilitate, integrate and secure communication up and down the technology stack…

Generate Ansible Playbooks faster by using watsonx Code Assistant for Red Hat Ansible Lightspeed

2 min read - IBM watsonx™ Code Assistant is a suite of products designed to support AI-assisted code development and application modernization. Within this suite, IBM watsonx Code Assistant for Red Hat® Ansible® Lightspeed equips developers with generative AI (gen AI) capabilities, accelerating the creation of Ansible Playbooks. In early 2024, IBM watsonx Code Assistant for Red Hat Ansible Lightspeed introduced model customization and a no-cost 30-day trial. Building on this momentum, we are excited to announce the on-premises release of watsonx Code Assistant for Red Hat Ansible Lightspeed,…

4 key metrics to know when monitoring microservices applications running on Kubernetes

3 min read - Understanding how microservice applications works on Kubernetes is important in software development. In this article, we will discuss why observing microservice applications on Kubernetes is crucial and several metrics that you should focus on as part of your observability strategy. Why should you observe microservice health running on Kubernetes and what are the Kubernetes metrics you should monitor? Consider a large e-commerce platform that utilizes microservices architecture deployed on Kubernetes clusters. Each microservice, responsible for specific functionalities such as inventory…

IBM Newsletters

Get our newsletters and topic updates that deliver the latest thought leadership and insights on emerging trends.
Subscribe now More newsletters