cool DNS tool

Here is a nice tool to help one get a better grip on the process that a DNS server has to go though to resolve hostnames:

Trace DNS Delegation

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

NOLAJ

That's pretty cool.

exampasser

Had a little bit of fun yesterday and make my own small-scale DNS hierarchy (plan to focus on DNSSEC next)[FONT=Arial, Helvetica, sans-serif][/FONT].

MentholMoose

You can do something like this with dig (*nix) with the +trace option, or nslookup (*nix and Windows) with debug. Here's dig:

$ dig @8.8.8.8 -t A www.google.com +trace

; <<>> DiG 9.8.1 <<>> @8.8.8.8 -t A www.google.com +trace
; (1 server found)
;; global options: +cmd
.                       32913   IN      NS      a.root-servers.net.
.                       32913   IN      NS      h.root-servers.net.
.                       32913   IN      NS      b.root-servers.net.
.                       32913   IN      NS      j.root-servers.net.
.                       32913   IN      NS      c.root-servers.net.
.                       32913   IN      NS      d.root-servers.net.
.                       32913   IN      NS      e.root-servers.net.
.                       32913   IN      NS      f.root-servers.net.
.                       32913   IN      NS      m.root-servers.net.
.                       32913   IN      NS      i.root-servers.net.
.                       32913   IN      NS      g.root-servers.net.
.                       32913   IN      NS      l.root-servers.net.
.                       32913   IN      NS      k.root-servers.net.
;; Received 228 bytes from 8.8.8.8#53(8.8.8.[IMG]https://us.v-cdn.net/6030959/uploads/images/smilies/icon_cool.gif[/IMG] in 855 ms

com.                    172800  IN      NS      m.gtld-servers.net.
com.                    172800  IN      NS      h.gtld-servers.net.
com.                    172800  IN      NS      i.gtld-servers.net.
com.                    172800  IN      NS      g.gtld-servers.net.
com.                    172800  IN      NS      l.gtld-servers.net.
com.                    172800  IN      NS      d.gtld-servers.net.
com.                    172800  IN      NS      e.gtld-servers.net.
com.                    172800  IN      NS      c.gtld-servers.net.
com.                    172800  IN      NS      b.gtld-servers.net.
com.                    172800  IN      NS      a.gtld-servers.net.
com.                    172800  IN      NS      f.gtld-servers.net.
com.                    172800  IN      NS      j.gtld-servers.net.
com.                    172800  IN      NS      k.gtld-servers.net.
;; Received 504 bytes from 192.203.230.10#53(192.203.230.10) in 593 ms

google.com.             172800  IN      NS      ns2.google.com.
google.com.             172800  IN      NS      ns1.google.com.
google.com.             172800  IN      NS      ns3.google.com.
google.com.             172800  IN      NS      ns4.google.com.
;; Received 168 bytes from 192.5.6.30#53(192.5.6.30) in 375 ms

www.google.com.         604800  IN      CNAME   www.l.google.com.
www.l.google.com.       300     IN      A       74.125.224.212
www.l.google.com.       300     IN      A       74.125.224.209
www.l.google.com.       300     IN      A       74.125.224.208
www.l.google.com.       300     IN      A       74.125.224.211
www.l.google.com.       300     IN      A       74.125.224.210
;; Received 132 bytes from 216.239.32.10#53(216.239.32.10) in 70 ms

undomiel

I knew about dig but didn't know you could pull the same trace from nslookup. Good info to know! It'll help the next time I'm explaining DNS to someone.