Making unbound-anchor very verbose
edward.lewis at icann.org
Tue Sep 22 19:27:28 UTC 2015
Thanks. That has kicked me off in some direction.
On 9/21/15, 11:02, "Unbound-users on behalf of unbound-users at unbound.net"
<unbound-users-bounces at unbound.net on behalf of unbound-users at unbound.net>
>-----BEGIN PGP SIGNED MESSAGE-----
>It does not say a lot because all it does is do an UDP query, see that
>it works, and exit. If you add, say, -F (force TLS update), then
>it'll print out a lot of info (with -vvvv). Like, https headers, ssl
>certificates, xml contents ...
>Best regards, Wouter
>On 14/09/15 18:56, Edward Lewis via Unbound-users wrote:
>> D'oh - smallapp/...
>> On 9/14/15, 12:04, "Edward Lewis" <edward.lewis at icann.org> wrote:
>>> I'd like to have unbound-anchor be (able to be) much more
>>> $ unbound-anchor -a testroot.key $ unbound-anchor -a testroot.key
>>> -v testroot.key has content success: the anchor is ok $
>>> unbound-anchor -a testroot.key -vvvvv testroot.key has content
>>> success: the anchor is ok $ unbound-anchor -a testroot.key -v -v
>>> -v -v testroot.key has content success: the anchor is ok
>>> I.e., the latter two ought to "show the work done." I'm more
>>> interested in the process than obtaining the result (so long as
>>> the result is as expected).
>>> I'm not too familiar with unbound distributions. Where (in what
>>> files) can I add print/echo statements to do this? (I don't have
>>> specific statements to add, I need to prototype it.) I just
>>> don't read script well enough I guess. ;)
>-----BEGIN PGP SIGNATURE-----
>Version: GnuPG v2
>-----END PGP SIGNATURE-----
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 4604 bytes
Desc: not available
More information about the Unbound-users