Unboundtest.com serving more informative DNSSEC error logs

[jsha]

I've updated unboundtest.com to add these configuration fields:

    val-log-level: 2
    ede: yes

From the unbound documentation:

   val-log-level: <number>
          Have the validator print validation failures to  the  log.   Re-
          gardless  of  the  verbosity setting.  Default is 0, off.  At 1,
          for every user query that fails a line is printed to  the  logs.
          This  way  you  can monitor what happens with validation.  Use a
          diagnosis tool, such as dig or drill, to find out why validation
          is  failing  for  these  queries.  At 2, not only the query that
          failed is printed but also the reason why Unbound thought it was
          wrong and which server sent the faulty data.
   ede: <yes or no>
        If  enabled,  Unbound  will  respond with Extended DNS Error codes
        (RFC8914).  These EDEs attach informative error messages to a  re-
        sponse for various errors. Default is "no".

        When the val-log-level option is also set to 2, responses with Ex-
        tended DNS Errors concerning DNSSEC failures that are  not  served
        from cache, will also contain a descriptive text message about the
        reason for the failure.

This will hopefully make it a little easier to diagnose DNSSEC-related problems. Here's some example output for dnssec-failed.org:

May 15 19:12:14 unbound[1384:0] info: Did not match a DS to a DNSKEY, thus bogus.
May 15 19:12:14 unbound[1384:0] info: Could not establish a chain of trust to keys for dnssec-failed.org. DNSKEY IN
May 15 19:12:14 unbound[1384:0] info: validation failure <dnssec-failed.org. CAA IN>: no keys have a DS with algorithm RSASHA1 from 2001:558:100e:5:68:87:72:244 for key dnssec-failed.org. while building chain of trust