I recently became familiarized with dig or domain information groper, or in short it is the outstanding tool for DNS lookups. It has great functionally ant it is preinstalled on most of the distributions today.If we don't tell it to query a specific name server, dig will try each of the servers listed in /etc/resolv.conf.
The command goes something like this:
dig [ @server ] [ -b address ] [ -c class ] [ -f filename ] [ -k filename ] [ -p port# ] [ -t type ] [ -x addr ] [ -y name:key ] [ name ] [ type ] [ class ] [ queryopt... ]
dig [ -h ]
dig [ global-queryopt... ] [ query... ]
Examples
Or why I use dig mostly for. Let say I want to see all the redirects from the top level ns to my server.
dig mitemitreski.com +trace and we get something like this:
; <<>> DiG 9.7.1-P2 <<>> mitemitreski.com +trace ;; global options: +cmd . 46703 IN NS b.root-servers.net. . 46703 IN NS k.root-servers.net. . 46703 IN NS c.root-servers.net. . 46703 IN NS e.root-servers…
The command goes something like this:
dig [ @server ] [ -b address ] [ -c class ] [ -f filename ] [ -k filename ] [ -p port# ] [ -t type ] [ -x addr ] [ -y name:key ] [ name ] [ type ] [ class ] [ queryopt... ]
dig [ -h ]
dig [ global-queryopt... ] [ query... ]
Examples
Or why I use dig mostly for. Let say I want to see all the redirects from the top level ns to my server.
dig mitemitreski.com +trace and we get something like this:
; <<>> DiG 9.7.1-P2 <<>> mitemitreski.com +trace ;; global options: +cmd . 46703 IN NS b.root-servers.net. . 46703 IN NS k.root-servers.net. . 46703 IN NS c.root-servers.net. . 46703 IN NS e.root-servers…