{"id":1793,"date":"2010-05-10T01:56:08","date_gmt":"2010-05-10T07:56:08","guid":{"rendered":"http:\/\/gregsowell.com\/?p=1793"},"modified":"2010-05-07T14:57:01","modified_gmt":"2010-05-07T20:57:01","slug":"tracing-dns-servers-with-dig","status":"publish","type":"post","link":"https:\/\/gregsowell.com\/?p=1793","title":{"rendered":"Tracing DNS Servers With Dig"},"content":{"rendered":"<p>For the people that like to see the hops that their DNS entries take, there is the trace option in Dig.  If you are trying to diagnose DNS SOA issues with forward or reverse zones, this is a must!<\/p>\n<p>Forward traces:<\/p>\n<pre class=\"gs-code\"><code class=\"language-plaintext\">dig gregsowell.com +trace<\/code><\/pre>\n<pre class=\"gs-code\"><code class=\"language-plaintext\">[root@dns2 ~]# dig gregsowell.com +trace\r\n\r\n; &lt;&lt;&gt;&gt; DiG 9.2.4 &lt;&lt;&gt;&gt; gregsowell.com +trace\r\n;; global options:  printcmd\r\n.                       178662  IN      NS      i.root-servers.net.\r\n.                       178662  IN      NS      j.root-servers.net.\r\n.                       178662  IN      NS      k.root-servers.net.\r\n.                       178662  IN      NS      l.root-servers.net.\r\n.                       178662  IN      NS      m.root-servers.net.\r\n.                       178662  IN      NS      a.root-servers.net.\r\n.                       178662  IN      NS      b.root-servers.net.\r\n.                       178662  IN      NS      c.root-servers.net.\r\n.                       178662  IN      NS      d.root-servers.net.\r\n.                       178662  IN      NS      e.root-servers.net.\r\n.                       178662  IN      NS      f.root-servers.net.\r\n.                       178662  IN      NS      g.root-servers.net.\r\n.                       178662  IN      NS      h.root-servers.net.\r\n;; Received 500 bytes from 209.189.224.40#53(209.189.224.40) in 1 ms\r\n\r\ncom.                    172800  IN      NS      d.gtld-servers.net.\r\ncom.                    172800  IN      NS      g.gtld-servers.net.\r\ncom.                    172800  IN      NS      j.gtld-servers.net.\r\ncom.                    172800  IN      NS      i.gtld-servers.net.\r\ncom.                    172800  IN      NS      c.gtld-servers.net.\r\ncom.                    172800  IN      NS      f.gtld-servers.net.\r\ncom.                    172800  IN      NS      m.gtld-servers.net.\r\ncom.                    172800  IN      NS      l.gtld-servers.net.\r\ncom.                    172800  IN      NS      b.gtld-servers.net.\r\ncom.                    172800  IN      NS      e.gtld-servers.net.\r\ncom.                    172800  IN      NS      h.gtld-servers.net.\r\ncom.                    172800  IN      NS      k.gtld-servers.net.\r\ncom.                    172800  IN      NS      a.gtld-servers.net.\r\n;; Received 504 bytes from 192.36.148.17#53(i.root-servers.net) in 43 ms\r\n\r\ngregsowell.com.         172800  IN      NS      dns1.managednetworks.com.\r\ngregsowell.com.         172800  IN      NS      dns2.managednetworks.com.\r\n;; Received 118 bytes from 192.31.80.30#53(d.gtld-servers.net) in 29 ms\r\n\r\ngregsowell.com.         38400   IN      A       209.189.228.152\r\ngregsowell.com.         38400   IN      NS      dns1.managednetworks.com.\r\ngregsowell.com.         38400   IN      NS      dns2.managednetworks.com.\r\ngregsowell.com.         38400   IN      NS      dns3.managednetworks.com.\r\n;; Received 169 bytes from 209.189.224.40#53(dns1.managednetworks.com) in 0 ms<\/code><\/pre>\n<p>Reverse traces:<\/p>\n<pre class=\"gs-code\"><code class=\"language-plaintext\">dig -x 209.189.228.152 +trace<\/code><\/pre>\n<pre class=\"gs-code\"><code class=\"language-plaintext\">[root@dns2 ~]# dig -x 209.189.228.152 +trace\r\n\r\n; &lt;&lt;&gt;&gt; DiG 9.2.4 &lt;&lt;&gt;&gt; -x 209.189.228.152 +trace\r\n;; global options:  printcmd\r\n.                       178553  IN      NS      m.root-servers.net.\r\n.                       178553  IN      NS      a.root-servers.net.\r\n.                       178553  IN      NS      b.root-servers.net.\r\n.                       178553  IN      NS      c.root-servers.net.\r\n.                       178553  IN      NS      d.root-servers.net.\r\n.                       178553  IN      NS      e.root-servers.net.\r\n.                       178553  IN      NS      f.root-servers.net.\r\n.                       178553  IN      NS      g.root-servers.net.\r\n.                       178553  IN      NS      h.root-servers.net.\r\n.                       178553  IN      NS      i.root-servers.net.\r\n.                       178553  IN      NS      j.root-servers.net.\r\n.                       178553  IN      NS      k.root-servers.net.\r\n.                       178553  IN      NS      l.root-servers.net.\r\n;; Received 500 bytes from 209.189.224.40#53(209.189.224.40) in 1 ms\r\n\r\n209.in-addr.arpa.       86400   IN      NS      W.ARIN.NET.\r\n209.in-addr.arpa.       86400   IN      NS      V.ARIN.NET.\r\n209.in-addr.arpa.       86400   IN      NS      Z.ARIN.NET.\r\n209.in-addr.arpa.       86400   IN      NS      U.ARIN.NET.\r\n209.in-addr.arpa.       86400   IN      NS      X.ARIN.NET.\r\n209.in-addr.arpa.       86400   IN      NS      DILL.ARIN.NET.\r\n209.in-addr.arpa.       86400   IN      NS      Y.ARIN.NET.\r\n;; Received 169 bytes from 202.12.27.33#53(m.root-servers.net) in 195 ms\r\n\r\n228.189.209.in-addr.arpa. 86400 IN      NS      dns1.managednetworks.com.\r\n228.189.209.in-addr.arpa. 86400 IN      NS      dns3.managednetworks.com.\r\n228.189.209.in-addr.arpa. 86400 IN      NS      dns2.managednetworks.com.\r\n;; Received 122 bytes from 72.52.71.2#53(W.ARIN.NET) in 39 ms\r\n\r\n152.228.189.209.in-addr.arpa. 38400 IN  PTR     152.228.189.209.managednetworks.com.\r\n228.189.209.in-addr.arpa. 38400 IN      NS      dns2.managednetworks.com.\r\n228.189.209.in-addr.arpa. 38400 IN      NS      dns3.managednetworks.com.\r\n228.189.209.in-addr.arpa. 38400 IN      NS      dns1.managednetworks.com.\r\n;; Received 200 bytes from 209.189.224.40#53(dns1.managednetworks.com) in 0 ms<\/code><\/pre>\n","protected":false},"excerpt":{"rendered":"<p>For the people that like to see the hops that their DNS entries take, there is the trace option in Dig. If you are\u2026<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14,13],"tags":[],"class_list":["post-1793","post","type-post","status-publish","format-standard","hentry","category-linux","category-server"],"_links":{"self":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/1793","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1793"}],"version-history":[{"count":3,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/1793\/revisions"}],"predecessor-version":[{"id":1796,"href":"https:\/\/gregsowell.com\/index.php?rest_route=\/wp\/v2\/posts\/1793\/revisions\/1796"}],"wp:attachment":[{"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1793"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1793"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gregsowell.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1793"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}