This happens when ldns is built with +libressl.
Fixing the title how it was before. Note that this is an issue when ldns is built with libressl. ldns-utils doesn't have a libressl USE flag or rely on openssl or libressl.
So what to do? I can add a blocker to libressl until upstream fixes this… Or does anybody have some patch that will ix it?
Does this problem still exist with 1.7.0?