Maintained by: NLnet Labs

[Unbound-users] NXDOMAIN for forwarded zones after some time

Nagy, Attila
Wed Feb 25 14:16:54 CET 2015


Hi,

I have some unbounds (well, mostly -or exclusively, haven't checked yet- 
the FreeBSD shipped 1.4.22) with some local (intranet) zones forwarded.
Sometimes after something happens unbound starts to give NXDOMAIN for 
these records. Sadly it happens very infrequently, so I don't have any 
verbose info on that currently. (but will collect them if I know what to do)

The zones in question are configured like that:
         private-domain: domain.intra
         domain-insecure: domain.intra
         private-domain: domain.intra2
         domain-insecure: domain.intra2
stub-zone:
         name: domain.intra
         stub-addr: 172.28.18.1

stub-zone:
         name: domain.intra2
         stub-addr: 172.28.18.1

Where 172.28.18.1 is a bind server, which gives back NS records like this:
domain.intra name server ns1.domain.intra2
domain.intra name server ns2.domain.intra

When I start unbound, the resolution works. Sometimes it works for weeks 
or months, then suddenly fails.

What could cause this and what should I report if I can reproduce it?

Thanks,