Re: Response Policy Zone: disabling "leaking" of lookups

2020-09-02 Thread Carl Byington via bind-users
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2020-09-02 at 17:47 -0700, Fred Morris wrote: > how do I disable the (useless) resolution directed at upstream > servers? Isn't that just "qname-wait-recurse no;" -BEGIN PGP SIGNATURE-

Response Policy Zone: disabling "leaking" of lookups

2020-09-02 Thread Fred Morris
It comes to my attention that when an unresolvable query occurs, it gets forwarded to the authoritative zone regardless of anything I can set in named.conf. Closest I can come is qname-wait-recurse which has the /opposite/ effect sort of, namely waiting for recursion to complete. If I have

"forward first" set on a master zone not working as expected

2020-09-02 Thread Taylor Vierrether via bind-users
Hello, I am attempting to set up an internal DNS server that is authoritative for internal resources, but also will respond for external resources on the same domain that it does not have records for. For example, I have a domain sub.example.com , and I want to have

Re: bind 9.16.6 on FreeBSD - Assert

2020-09-02 Thread Borja Marcos
> On 2 Sep 2020, at 09:15, Søren Andersen wrote: > > It looks like the same bug to me. - Did you try to patch your source code > with the path isc just made? No, I am not aware of a patch. I have rolled it back to 9.11 for now, it’s a production server. Thanks, Borja.

Re: bind 9.16.6 on FreeBSD - Assert

2020-09-02 Thread Søren Andersen
It looks like the same bug to me. - Did you try to patch your source code with the path isc just made? From: Borja Marcos Sent: Wednesday, September 2, 2020 08:39 To: Søren Andersen Cc: bind-users@lists.isc.org Subject: Re: bind 9.16.6 on FreeBSD - Assert

Re: bind 9.16.6 on FreeBSD - Assert

2020-09-02 Thread Borja Marcos
> On 1 Sep 2020, at 19:48, Søren Andersen wrote: > > hmm.. I think you hit this bug right here: > https://gitlab.isc.org/isc-projects/bind9/-/issues/2104 Looks like that. I compiled bind with debug symbols and it crashed again. No way to append this to your bug report, it’s closed.