serve-expired seems to break flush_zone

Hi all, I have a simple forward-everything setup with serve-expired enabled: server: serve-expired: yes forward-zone: name: . forward-addr: X.X.X.X If I use "flush_zone ." to clear the cache, I still get cache hits for supposedly-

Re: serve-expired seems to break flush_zone

On 2018-04-06 02:47 AM, W.C.A. Wijngaards via Unbound-users wrote: Hi Marc, On 04/04/18 20:29, Marc Branchaud via Unbound-users wrote: Hi all, I have a simple forward-everything setup with serve-expired enabled: server:     serve-expired: yes forward-zone:     name

Re: serve-expired seems to break flush_zone

. Wijngaards via Unbound-users wrote: Hi Marc, On 04/04/18 20:29, Marc Branchaud via Unbound-users wrote: Hi all, I have a simple forward-everything setup with serve-expired enabled:  server: serve-expired: yes  forward-zone: name: . forward-addr: X.X.X.X If I

TLS and local unbound-control

Hi all, (Please bear with me in the following; some of this might be mere correlation and not causation.) I've recently switched from OpenSSL 0.9.8 to 1.0.1. I've noticed that my unbound-control commands now take significantly longer to complete. The "stats" command in particular takes ~3 s

Re: TLS and local unbound-control

On 2018-05-04 04:21 PM, Simon Deziel via Unbound-users wrote: Hi Marc, On 2018-05-04 04:12 PM, Marc Branchaud via Unbound-users wrote: So I'd like to request that: (a) unbound-control avoids using TLS when communicating over a local socket You can use "control-use-cert: no"

Re: TLS and local unbound-control

On 2018-05-04 04:12 PM, Marc Branchaud via Unbound-users wrote: Hi all, (Please bear with me in the following; some of this might be mere correlation and not causation.) I've recently switched from OpenSSL 0.9.8 to 1.0.1.  I've noticed that my unbound-control commands now take sig