I noticed on 2017 April 30 that running q.exe -dnssec -check -anchor ../bit.key @127.0.0.1 bluishcoder.bit produces the error dns: bad key. Using the ZSK instead works fine.
It's not entirely clear to me what the expected behavior here is. @hlandau 's comment on Matrix was "I find the behaviour of q.exe there extremely peculiar. Unbound validates from a KSK so it seems likely to be a q.exe issue". We probably should look into this more closely (maybe it's been fixed in the year since I noticed it?), and maybe report the issue upstream to q.
I noticed on 2017 April 30 that running
q.exe -dnssec -check -anchor ../bit.key @127.0.0.1 bluishcoder.bitproduces the errordns: bad key. Using the ZSK instead works fine.It's not entirely clear to me what the expected behavior here is. @hlandau 's comment on Matrix was "I find the behaviour of q.exe there extremely peculiar. Unbound validates from a KSK so it seems likely to be a q.exe issue". We probably should look into this more closely (maybe it's been fixed in the year since I noticed it?), and maybe report the issue upstream to q.