CompuRoot

@yhakbar Yes, it looks like it compiled now correctly against musl, so let close the issue

> When looking up the addresses for nameservers, unbound encounters too many NXDOMAIN responses for those lookup and stops to avoid causing a denial of service. Such workflow might work...

> So that should not be an issue, for the test of an IP address lookup. Looks like an issue: ``` Mar 07 18:14:24 unbound[24059:1] error: SERVFAIL : exceeded the...

BTW, are these `servfails` below are related to the same case? ``` Mar 01 10:20:20 unbound[8110:3] info: 127.0.0.1 1.0.0.127.bl.spameatingmonkey.net. A IN SERVFAIL 0.068697 0 62 Mar 01 10:20:25 unbound[8110:0] info:...

> The issues from the logs are that the nameservers are NXDOMAIN. But those aren't NXDOMAIN after `unbound` been restated. Those (as well any other that frequently queried) became NXDOMAIN...

Thank you for the suggestion, yes, `qname-minimisation` it turned on on those servers. I will turn it off and will update if it resolves the issue

Unfortunately nothing helps. `unbound` can not be used on email servers where antispam solutions utilizing well known online services which use DNS to answer, - if IP registered in spam...

> Are there any other solutions? Yes, other resolvers. Unfortunately `unbound` is unusable on servers and border gateways due to hard-coding on number of sends. Because of this, we removed...

> But why would that fail so hard, I mean 30 packets is a lot, most DNS queries should work in only several. If unbound supposed to work on a...

> The maximum nameserver nxdomains exceeded error, is an error from the recursion, No. It doesn't work like a regular DNS query. To be able to prevent abuse and commercialize...