[talk] NSD and reverse zone files

[Okan Demirmen]

On Thu 2016.06.30 at 12:13 -0400, Mark Saad wrote:
> 
> > On Jun 30, 2016, at 11:05 AM, Patrik Lundin <patrik at sigterm.se> wrote:
> > 
> >> On Thu, Jun 30, 2016 at 06:56:10PM +0530, Sujit K M wrote:
> >>> On Thu, Jun 30, 2016 at 11:53 AM, Patrik Lundin <patrik at sigterm.se> wrote:
> >>>> On Tue, Jun 28, 2016 at 01:19:36PM +0000, Mark Saad wrote:
> >>>>  Some further checking . I have unbound in front of nsd; and it appears that unbound is the issue.
> >>> 
> >>> Just a quick hint: it was possible to see something was in front of NSD
> >>> becuase your drill output contained "flags: [...] ra". Since NSD is
> >>> authoritative only it should never set the Recursion Available bit.
> >> 
> >> But isn't unbound something that does this?
> > 
> > Yes of course. I was just pointing out that the drill command was
> > indicating that we were not actually contacting NSD prior to it being
> > clarified later in the thread.
> > 
> > -- 
> > Patrik Lundin
> > 
> 
> Pat
>    I have to dig int the unbound config options ; the openbsd mailing lists have a similar thread about this but I am stumped. You are right that Unbound isn't passing the query on . 

your unbound.conf needs to be told about this space, something like:

	local-zone: "168.192.in-addr.arpa." nodefault
	stub-zone:
		name: "168.192.in-addr.arpa."
		stub-addr: [your nsd ip:port]