Re: Scripting dnssec-verify - processing command output

2021-02-07 Thread Matthew Richardson
ks to see whether they think this is a bug... Best wishes, Matthew -- >From: Paul Kosinski via bind-users >To: bind-users@lists.isc.org >Cc: >Date: Sat, 6 Feb 2021 19:45:54 -0500 >Subject: Re: Scripting dnssec-verify - processing command output >It sounds to me like dnssec-veri

Re: Scripting dnssec-verify - processing command output

2021-02-07 Thread @lbutlr
On 06 Feb 2021, at 17:45, Paul Kosinski via bind-users wrote: > It sounds to me like dnssec-verify is sending the output in question to > STDERR instead of STDOUT. Dnssec-verify sends errors (like missing /Bad/Expected lines) to stderr, it sends status warnings like "The zone is not fully

Re: Scripting dnssec-verify - processing command output

2021-02-06 Thread Paul Kosinski via bind-users
It sounds to me like dnssec-verify is sending the output in question to STDERR instead of STDOUT. On Sat, 06 Feb 2021 19:02:28 + Matthew Richardson wrote: > I have been using Perl to do a reasonable amount of scripting, running bind > utilities and processing the results into variables.

Scripting dnssec-verify - processing command output

2021-02-06 Thread Matthew Richardson
I have been using Perl to do a reasonable amount of scripting, running bind utilities and processing the results into variables. The details below are from Bind 9.11.27 on Centos 7. The code:- $resp = `dig -t soa example.com`; print "dig resp:'$resp'\n"; gets the result of the dig