On 2018-04-09 03:40 AM, W.C.A. Wijngaards wrote:
Hi Marc,
I can confirm that the patch fixes my test case (in 1.6.7).
The documentation update also looks good.
Thanks for the quick response!
M.
On 06/04/18 17:05, Marc Branchaud wrote:
On 2018-04-06 02:47 AM, W.C.A.
Hi Marc,
On 06/04/18 17:05, Marc Branchaud wrote:
> 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:
>>>
>>>
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: .
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 use "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
