On Saturday, July 26, 2014 17:35 CEST, Sonic <sonicsm...@gmail.com> wrote:
> On Sat, Jul 26, 2014 at 11:21 AM, Sonic <sonicsm...@gmail.com> wrote:
> > If you're just using a /24 as your access-control seems to indicate
> > try replacing the above with (this works great for me):
> > local-zone: "0.0.10.in-addr.arpa." transparent
> >
> > and update the stub-zone name to read:
> > name: "0.0.10.in-addr.arpa."
>
> And, of course you NSD zone name must be:
> zone:
> name: "0.0.10.in-addr.arpa"
> zonefile: "10.0.0.zone"
>
> (although the zonefile doesn't have to strictly be named as such)
I indeed only use a /24, so I changed as you suggested, and it seems to help.
But the problem was not apparrent all the time, will monitor it, if it comes
back with this new configuration, hope not.
Anyways, I still find it odd, that it worked only halfway with the other
configuration I had before, and a simple restart of unbound fixed it.
thanks,
Sebastian
