{"id":366,"date":"2010-08-13T06:10:11","date_gmt":"2010-08-13T12:10:11","guid":{"rendered":"http:\/\/blog.supportpro.com\/2010\/08\/usage-of-dig-command-for-finding-the-dns-information\/"},"modified":"2026-03-27T00:56:44","modified_gmt":"2026-03-27T06:56:44","slug":"usage-of-dig-command-for-finding-the-dns-information","status":"publish","type":"post","link":"https:\/\/www.supportpro.com\/blog\/usage-of-dig-command-for-finding-the-dns-information\/","title":{"rendered":"Complete Guide to Using the DIG Command for DNS Troubleshooting"},"content":{"rendered":"\n<p>The <strong><code>dig<\/code> (Domain Information Groper)<\/strong> command is a powerful DNS troubleshooting tool used to query name servers and retrieve detailed information about domain records such as <strong>A, MX, NS, TXT, SOA<\/strong>, and more.<\/p>\n\n\n\n<p>System administrators widely use dig to diagnose DNS issues, verify domain configurations, and trace DNS resolution paths.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>What is the DIG Command?<\/strong><\/h2>\n\n\n\n<p>The dig command queries DNS servers and displays how a domain name resolves to an IP address.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Basic Example<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig live.com<\/code><\/pre>\n\n\n\n<p>This command returns:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>DNS query status<\/li>\n\n\n\n<li>Answer section (IP address)<\/li>\n\n\n\n<li>Query time<\/li>\n\n\n\n<li>DNS server used for resolution<\/li>\n<\/ul>\n\n\n\n<p>By default, dig queries your system\u2019s <strong>configured resolver<\/strong>, meaning the results may come from cached DNS data.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Querying a Specific Nameserver<\/strong><\/h2>\n\n\n\n<p>To bypass cached results and get authoritative DNS information, query the domain\u2019s nameserver directly:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig @ns1.msft.net live.com<\/code><\/pre>\n\n\n\n<p>This provides real-time data directly from the authoritative DNS server.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Understanding Root Name Servers<\/strong><\/h2>\n\n\n\n<p>Running dig without arguments displays <strong>root DNS servers<\/strong>:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig<\/code><\/pre>\n\n\n\n<p>Root nameservers store information about <strong>Top-Level Domains (TLDs)<\/strong> such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li><code>.com<\/code><\/li>\n\n\n\n<li><code>.net<\/code><\/li>\n\n\n\n<li><code>.org<\/code><\/li>\n\n\n\n<li>country domains like <code>.us<\/code><\/li>\n<\/ul>\n\n\n\n<p>They do not store individual domain records but instead point to the next DNS level.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Finding TLD Nameservers<\/strong><\/h2>\n\n\n\n<p>To locate nameservers responsible for a TLD:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig us NS<\/code><\/pre>\n\n\n\n<p>This lists authoritative nameservers managing the <code>.us<\/code> domain zone.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Reverse DNS Delegation Process<\/strong><\/h2>\n\n\n\n<p>DNS resolution follows a hierarchical structure:<\/p>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Root nameservers<\/li>\n\n\n\n<li>TLD nameservers<\/li>\n\n\n\n<li>Domain nameservers<\/li>\n\n\n\n<li>Final DNS records<\/li>\n<\/ol>\n\n\n\n<p>Example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig @a.cctld.us linux.us NS<\/code><\/pre>\n\n\n\n<p>This retrieves nameservers responsible for the domain.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Checking SOA (Start of Authority) Record<\/strong><\/h2>\n\n\n\n<p>The SOA record contains essential DNS zone details:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig @ns1.webhost.us linux.us SOA<\/code><\/pre>\n\n\n\n<p>SOA includes:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Primary nameserver<\/li>\n\n\n\n<li>Administrator email<\/li>\n\n\n\n<li>Serial number<\/li>\n\n\n\n<li>Refresh and retry intervals<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Common DIG Record Lookups<\/strong><\/h2>\n\n\n\n<h3 class=\"wp-block-heading\">1. Check A Record<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig +short @ns1.webhost.us www.linux.us A<\/code><\/pre>\n\n\n\n<p>Returns the domain\u2019s IP address.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">2. Check MX Record (Mail Server)<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig +short @ns1.webhost.us linux.us MX<\/code><\/pre>\n\n\n\n<p>Displays mail server configuration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">3. Check SPF Record<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig +short @ns1.google.com google.com TXT<\/code><\/pre>\n\n\n\n<p>Used to verify sender authorization for email delivery.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">4. Check DKIM \/ DomainKey Record<\/h3>\n\n\n\n<pre class=\"wp-block-code\"><code>dig +short @ns1.yahoo.com _domainkey.yahoo.com TXT<\/code><\/pre>\n\n\n\n<p>Helps validate email authenticity.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Tracing DNS Resolution Path<\/strong><\/h2>\n\n\n\n<p>Similar to traceroute for networks, dig can trace DNS delegation using:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>dig google.com +trace<\/code><\/pre>\n\n\n\n<p>This command shows:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Root servers contacted<\/li>\n\n\n\n<li>TLD nameservers<\/li>\n\n\n\n<li>Authoritative domain nameservers<\/li>\n\n\n\n<li>Final DNS resolution result<\/li>\n<\/ul>\n\n\n\n<p>It provides complete visibility into how DNS queries travel across the internet.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Why DIG is Important<\/strong><\/h2>\n\n\n\n<p>Using dig helps administrators:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Troubleshoot DNS propagation issues<\/li>\n\n\n\n<li>Verify domain configurations<\/li>\n\n\n\n<li>Validate email authentication records<\/li>\n\n\n\n<li>Identify incorrect DNS delegation<\/li>\n\n\n\n<li>Diagnose website accessibility problems<\/li>\n<\/ul>\n\n\n\n<h2 class=\"wp-block-heading\"><strong>Conclusion<\/strong><\/h2>\n\n\n\n<p>The dig command is an essential utility for DNS analysis and debugging. From simple record lookups to full DNS trace analysis, it offers precise insight into how domains resolve across global DNS infrastructure.<\/p>\n\n\n\n<p>If you require help,\u00a0<a href=\"https:\/\/www.supportpro.com\/requestquote.php\">contact SupportPRO Server Admin<\/a><span id=\"hs-cta-wrapper-9d590242-d641-4383-94b4-8cfd62f0af6b\" class=\"hs-cta-wrapper\"><span id=\"hs-cta-9d590242-d641-4383-94b4-8cfd62f0af6b\" class=\"hs-cta-node hs-cta-9d590242-d641-4383-94b4-8cfd62f0af6b\"><a href=\"https:\/\/www.supportpro.com\/freecheckup.php\"><\/a><\/span><\/span><\/p>\n\n\n\n<div class=\"wp-block-media-text alignwide has-media-on-the-right is-stacked-on-mobile is-vertically-aligned-center has-white-background-color has-background\"><div class=\"wp-block-media-text__content\">\n<p class=\"has-large-font-size\">Facing issues? <\/p>\n\n\n\n<p class=\"has-large-font-size\">Our technical support<br>engineers can solve it. <\/p>\n\n\n\n<!--HubSpot Call-to-Action Code --><span class=\"hs-cta-wrapper\" id=\"hs-cta-wrapper-3350a795-db50-482f-9911-301930d1b1be\"><span class=\"hs-cta-node hs-cta-3350a795-db50-482f-9911-301930d1b1be\" id=\"hs-cta-3350a795-db50-482f-9911-301930d1b1be\"><!--[if lte IE 8]><div id=\"hs-cta-ie-element\"><\/div><![endif]--><a href=\"https:\/\/cta-redirect.hubspot.com\/cta\/redirect\/2725694\/3350a795-db50-482f-9911-301930d1b1be\" ><img decoding=\"async\" class=\"hs-cta-img\" id=\"hs-cta-img-3350a795-db50-482f-9911-301930d1b1be\" style=\"border-width:0px;\" src=\"https:\/\/no-cache.hubspot.com\/cta\/default\/2725694\/3350a795-db50-482f-9911-301930d1b1be.png\"  alt=\"Contact Us today!\"\/><\/a><\/span><script charset=\"utf-8\" src=\"https:\/\/js.hscta.net\/cta\/current.js\"><\/script><script type=\"text\/javascript\"> hbspt.cta.load(2725694, '3350a795-db50-482f-9911-301930d1b1be', {\"useNewLoader\":\"true\",\"region\":\"na1\"}); <\/script><\/span><!-- end HubSpot Call-to-Action Code -->\n<\/div><figure class=\"wp-block-media-text__media\"><img fetchpriority=\"high\" decoding=\"async\" width=\"904\" height=\"931\" src=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png\" alt=\"guy server checkup\" class=\"wp-image-12943 size-full\" srcset=\"https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup.png 904w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-291x300.png 291w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-768x791.png 768w, https:\/\/www.supportpro.com\/blog\/wp-content\/uploads\/2022\/09\/Free-server-checkup-585x602.png 585w\" sizes=\"(max-width: 904px) 100vw, 904px\" \/><\/figure><\/div>\n","protected":false},"excerpt":{"rendered":"<p>The dig (Domain Information Groper) command is a powerful DNS troubleshooting tool used to query name servers and retrieve detailed information about domain records such as A, MX, NS, TXT,&hellip;<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_lmt_disableupdate":"","_lmt_disable":"","footnotes":""},"categories":[1],"tags":[],"class_list":["post-366","post","type-post","status-publish","format-standard","hentry","category-miscellaneous"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/comments?post=366"}],"version-history":[{"count":3,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/366\/revisions"}],"predecessor-version":[{"id":16759,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/posts\/366\/revisions\/16759"}],"wp:attachment":[{"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/media?parent=366"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/categories?post=366"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.supportpro.com\/blog\/wp-json\/wp\/v2\/tags?post=366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}