o it. (prefetch vs --enable-cache-ttl)
Sukmoon Lee
>
> > - Kevin
> >
> >
> >
> >
> > -Original Message-----
> > From: Mark Andrews [mailto:ma...@isc.org]
> > Sent: Thursday, August 04, 2016 7:47 PM
> > To: Darcy
> From: Mark Andrews [mailto:ma...@isc.org]
> Sent: Thursday, August 04, 2016 7:47 PM
> To: Darcy Kevin (FCA)
> Cc: bind-users@lists.isc.org
> Subject: Re: change response cache ttl (--enable-cache-ttl)
>
>
> In message , "Darcy
> Kevin (FCA
> )" writes:
>
rcy Kevin (FCA)
Cc: bind-users@lists.isc.org
Subject: Re: change response cache ttl (--enable-cache-ttl)
In message , "Darcy Kevin
(FCA)" writes:
> "many client have caused a burst DNS traffic" is not much of a problem
> statement, honestly.
>
> What does this patch
In message , "Darcy Kevin
(FCA)" writes:
> "many client have caused a burst DNS traffic" is not much of a problem
> statement, honestly.
>
> What does this patch add, of value, that isn't already covered by
> "max-cache-ttl"?
>
> If you're trying to allow the operators of intermediate resolvers t
016 2:32 PM
To: Darcy Kevin (FCA); bind-users@lists.isc.org
Subject: Re: change response cache ttl (--enable-cache-ttl)
Am 04.08.2016 um 20:27 schrieb Darcy Kevin (FCA):
> "many client have caused a burst DNS traffic" is not much of a problem
> statement, honestly.
>
> W
"many client have caused a burst DNS traffic" is not much of a problem
statement, honestly.
What does this patch add, of value, that isn't already covered by
"max-cache-ttl"?
If you're trying to allow the operators of intermediate resolvers to override
the intentions of the data owner, by enfo
6 matches
Mail list logo
