Re: unbound fetches DNS record from nsd but does not return it to client

On Tue, Aug 04, 2015 at 09:14:18AM +0200, W.C.A. Wijngaards wrote: Added text to address that. Thanks for pointing that out and the 'transparent' workaround for it. Looks good, thanks :). There is an NXDOMAIN at home. at .. DNSSEC does not allow data under an NXDOMAIN. If there

Re: unbound fetches DNS record from nsd but does not return it to client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Patrik, On 03/08/15 18:50, Patrik Lundin wrote: On Mon, Aug 03, 2015 at 12:42:00PM +0200, W.C.A. Wijngaards via Unbound-users wrote: I've fixed up the manual page and the example config file, and they now discuss configuring

Re: unbound fetches DNS record from nsd but does not return it to client

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi Patrik, On 01/08/15 10:33, Patrik Lundin via Unbound-users wrote: On Fri, Jul 31, 2015 at 10:36:34PM -0400, Sonic via Unbound-users wrote: I doubt that local-zone: 1.168.192.in-addr.arpa nodefault is necessary since you're defining it as a

Re: unbound fetches DNS record from nsd but does not return it to client

On Mon, Aug 03, 2015 at 12:42:00PM +0200, W.C.A. Wijngaards via Unbound-users wrote: I've fixed up the manual page and the example config file, and they now discuss configuring domain-insecure or local-zone nodefault for locally served zones. Thank you for making the configuration

Re: unbound fetches DNS record from nsd but does not return it to client

On Sat, Aug 1, 2015 at 4:33 AM, Patrik Lundin pat...@sigterm.se wrote: I again get the unbound default NXDOMAIN even if it looks like it matches what I want better. As you have pointed out to me on openbsd-misc in the past, the correct configuration to use in the latter case is this: ---

Re: unbound fetches DNS record from nsd but does not return it to client

thanks all! Got it, I think! Needed the domain-insecure bits, then reverse DNS was failing so I also needed to change the local-zone as Patrik mentioned. Complete unbound.conf now: Konsole output server: interface: 127.0.0.1 interface: 192.168.1.50 use-syslog: yes username: unbound

Re: unbound fetches DNS record from nsd but does not return it to client

On Fri, Jul 31, 2015 at 10:36:34PM -0400, Sonic via Unbound-users wrote: I doubt that local-zone: 1.168.192.in-addr.arpa nodefault is necessary since you're defining it as a stub-zone. This is actually necessary. I just tested on my firewall at home, and if I remove local-zone:

Re: unbound fetches DNS record from nsd but does not return it to client

On Fri, Jul 31, 2015 at 08:34:09PM -0500, Micah Yoder via Unbound-users wrote: Any pointers would be awesome. This is driving me nuts. Thanks! While I am not sure off the top of my head what is going wrong since you already have the do-not-query-localhost: no setting, I personally like to

unbound fetches DNS record from nsd but does not return it to client

Hi, First posted this to ServerFault without luck. Looks like it might be an unbound bug, or am I doing something wrong? *** This is a follow-up to

Re: unbound fetches DNS record from nsd but does not return it to client

First I'm not an expert but, I think you need to change access-control allow to allow_snoop. However, if its just your local network why not let unbound handle it. (something similar to below) local-zone: home. static local-data: datanet.home. IN A 192.168.1.61 local-zone: