Using dig +trace to understand DNS resolution from start to finish

The dig command is a robust device for troubleshooting queries and responses acquired from the Area Title Service (DNS). It’s put in by default on many working methods, together with Linux® and Mac OS X. It may be put in on Microsoft Home windows as a part of Cygwin. 

One of many many issues dig can do is to carry out recursive DNS decision and show the entire steps that it took in your terminal. That is extraordinarily helpful for understanding not solely how the DNS works, however for figuring out if there is a matter someplace throughout the decision chain that trigger decision failures in your zones or domains. 

First, let’s briefly overview how a question recursive receives a response in a typical recursive DNS decision situation: 

You because the DNS shopper (or stub resolver) question your recursive resolver for www.instance.com. 

Your recursive resolver queries the foundation nameserver for NS information for “com.” 

The basis nameserver refers your recursive resolver to the .com High-Stage Area (TLD) authoritative nameserver. 

Your recursive resolver queries the .com TLD authoritative server for NS information of “instance.com.” 

The .com TLD authoritative nameserver refers your recursive server to the authoritative servers for instance.com. 

Your recursive resolver queries the authoritative nameservers for instance.com for the A file for “www.instance.com” and receives 1.2.3.4 as the reply. 

Your recursive resolver caches the reply at some stage in the time-to-live (TTL) specified on the file and returns it to you.

The above course of principally appears to be like like this:

Step 1

Step 2

Step 3

Step 4

Step 5

This course of happens each time you sort a URL into your internet browser or hearth up your e mail shopper. This illustrates why DNS reply pace and accuracy are so vital: if the reply is inaccurate, you might have to repeat this course of a number of instances; and if the pace with which you obtain a solution is gradual, then it can make all the things you do on-line appear to take longer than it ought to.  

Driving each DNS reply pace and accuracy is on the core of the IBM® NS1 Join® worth proposition.   

Study extra at IBM NS1 Join