Possible stub/forward zone bug
qmail at top-consulting.net
Mon May 11 16:40:44 UTC 2020
I am facing with a weird issue, explained in a lot of detail
but I will sum it up here as well:
I am running Unbound 1.10 inside a FreeBSD environment.
I use a local domain named test.local served by Bind and cached by
Unbound is configured with:
I also tried configuring it as either a stub or a forward zone, it
doesn't matter as to the bug.
How to reproduce this:
- Start unbound
- resolve host1.test.local, host2.test.local, etc. all is fine
- resolve blah.local , it fails after trying to go to root NS's
- try to resolve host1.test.local, host2.test.local , it fails this
time with NXDOMAIN
If you restart Unbound, it will resolve test.local again, until you
try and resolve a non-configured .local domain
If I add "local" as a forward zone that goes to my main NS, the issue
goes away entirely.
Is this expected behavior or a bug ?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Unbound-users