Digging to the final IP
    Novosielski, Ryan 
    novosirj at ca.rutgers.edu
       
    Wed Oct 22 02:58:10 UTC 2014
    
    
  
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS      |---------------------*O*---------------------
||_// Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and Health | novosirj at rutgers.edu<mailto:novosirj at rutgers.edu>- 973/972.0922 (2x0922)
||  \\  Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
    `'
On Oct 21, 2014, at 16:00, Evan Hunt <each at isc.org<mailto:each at isc.org>> wrote:
On Tue, Oct 21, 2014 at 12:07:15PM -0700, Warren Kumari wrote:
dig A $name | awk '$0 ~ /status/ && $0 !~ /status: NOERROR,/ {
                       sub(",", "", $6 ); print $6; x=1
                  }
                  $4 == "A" { print $5; x=1 }
                  END { if (!x) print "TIMEOUT" }'
Because, not everyone is as stunningly brilliant as you?
To a non-zero population of this list the above looks like line-noise...
Could be worse, could be perl.  In any case, filtering the existing
output does seem better than adding every imaginable formatting option
to dig.
... I *could* maybe see adding a formatting option to produce an
easier-to-parse output header, though, such as:
       ; OPCODE=QUERY
       ; RCODE=NOERROR
       ; QRFLAG=1
       ; AAFLAG=0
       ; TCFLAG=0
       ; RDFLAG=1
       ; RAFLAG=1
       ; ADFLAG=0
       ; CDFLAG=0
       [... etc ...]
While on some level, I'm with you, "IP only" doesn't seem like a corner case.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20141021/bdf70484/attachment-0001.html>
    
    
More information about the bind-users
mailing list