[nsd-users] Unbound + NSD (stub-zones only needed for primary/secondary setup? NS records from the zone are ignored?)
amanda.constant at secure64.com
Sun Sep 30 08:47:29 UTC 2018
I am out of the office October 1st & 2nd and will respond to your message as quickly as possible once I return.
On Sep 30, 2018, at 2:28 AM, Anand Buddhdev via nsd-users <nsd-users at NLnetLabs.nl> wrote:
> On 29/09/2018 23:01, K. de Jong wrote:
> Hi K de Jong,
> Your question is actually about Unbound, and should be on the
> unbound-users mailing list. The fact that you're using NSD as an
> authoritative server is just incidental (your authoritative server could
> have been BIND, PowerDNS or Knot, and the same thing would happen).
> Anyway, about your question, see my answer below inline:
> The problem is that the secondary is never queried. I do flush the
> cache for the zone before I query again with dig/drill, but only the
> master does a query/response. The queries fail when I disable NSD on
> ns1 (primary).
> The behavior only changes when I also add the secondary address to the
> stub-zone in the Unbound config. But as far as I understand, the
> You need to add:
> stub-prime: yes
> to the relevant part of your unbound.conf. This will allow unbound to
> discover the secondary, and use it as well. See the unbound.conf man
> page for a detailed explanation.
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 1742 bytes
Desc: not available
More information about the nsd-users