> The primary cause of this is unbound is not a drop-in replacement for
> bind, they use different utilities, like unbound use drill, and bind use
> dig and friends.

Maybe I'm overlooking something, but that could be a problem with replacing
bind by unbound but not with linking unbound to the build. Currently we have
bind/nsd and apache/nginx all linked to the build.

Anyway I'm just curious, so no complaining intended.

Kind regards,


Martijn Rijkeboer

Reply via email to