sthaug at nethelp.no wrote: >> 3. How would a failure in passing the: "use-caps-for-id: yes" check be >> logged (warning or error)? > > Like this: > > [1218876864] unbound[9689:0] notice: wrong 0x20-ID in reply qname, answer dropped > [1218876864] unbound[9689:0] info: from server 62.212.64.121 port 53 > [1218876864] unbound[9689:0] info: for packet[79:0] B32C840000010001000000000236350332303102313702383507696E2D61646472046172706100000C0001C00C000C000100015180001809686F737465642D6279086C6561736577656203636F6D00 > > The above 0x20 failure is because the leaseweb.nl name servers, > > ns1.leaseweb.nl. A 62.212.64.121 > ns4.leaseweb.net. A 62.212.78.199 > ns5.leaseweb.nl. A 83.149.64.123 > > downcase everything, presumably because they are behind some sort of > load balancer. Ah, thank you! I now see a couple of these in my (big) logs :-) . I'll set my log monitor to look for unbound notices. (Would be useful if the subsequent two "info" entries were also "notice".)