Blocking ISSUES & Two Requests

[dnscrypt]

Blocking ISSUES & Two Requests

Which beta/alpha version are you using? Not having this problem on Linux.

[jedisct1]

Could you open one ticket per issue? That would be way easier to track.

DNSKEY is a record used to verify DNSSEC signatures. It's normal to see it if your clients support DNSSEC.
Maybe it did show up as a number instead of a name in the 1.x version. Or maybe it didn't work.

[jedisct1]

[empty domain names with DNSKEY queries]

Do you have a DNS cache between your clients and dnscrypt-proxy? Something like Unbound or dnsmasq?

What shows up as empty are queries for the root zone ("."). There's no domain name. Your caching resolver is trying to bubble up the DNS hierarchy to validate DNSSEC signatures, starting from the root.
So, this is a cosmetic issue. It should display a "." instead of something empty.

[jedisct1]

What wrong with time in the ltsv format?

Can you clarify what is wrong?

1516309968 corresponds to 2018-01-18 21:12:48 which doesn't look off.

This is a Unix timestamp. LTSV structured files are designed to be parsed by scripts, or by log processing applications.

[jedisct1]

Log management... after 2.0.0 is released.

[jedisct1]

I added a logged_qtypes filter, that you can use to choose what query types you want to see logged.

So you can log only A records if you want, and not see DNSKEY, NS and other records if you consider this is too verbose.