[PATCH] Remove upper limit of 10,000 for cache size
Signed-off-by: Dominik Derigs
---
src/option.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/src/option.c b/src/option.c
index 65df93a..180517a 100644
--- a/src/option.c
+++ b/src/option.c
@@ -2589,8 +2589,6 @@ static
---
man/dnsmasq.8| 2 +-
man/es/dnsmasq.8 | 3 ++-
man/fr/dnsmasq.8 | 3 ++-
3 files changed, 5 insertions(+), 3 deletions(-)
Note that this patch contains non-ASCII characters,
those might be mangled during transport ...
diff --git a/man/dnsmasq.8 b/man/dnsmasq.8
index 21069de..7664e06
On Wed, May 09, 2018 at 11:21:31AM +0200, Dominik DL6ER wrote:
> Geert Stappers wrote:
> > [ ... ] I'm trying to tell that the performance penality that Simon
> > warns us about, might by canceled by high computing power.
>
> I agree, but you should probably not be running a caching DNS server
Dear Geert and mailinglist members,
> Thing I wonder about is how the cache size clipping was discovered.
I recently sent a SIGUSR1 to our dnsmasq because a user said that some
queries have continuously been answered NXDOMAIN although they
shouldn't. As they have been answered within less than a
On 09/05/18 07:48, Harish Shetty wrote:
> HI
>
> I am upgrading the dnsmasq now, But I have couple of more question, I
> read somewhere, dnsmasq can cache only A, records only.. is that
> true??
A, (some) PTR and CNAME
and multiple line caching is not supported. Is there
HI
I am upgrading the dnsmasq now, But I have couple of more question, I
read somewhere, dnsmasq can cache only A, records only.. is that
true?? and multiple line caching is not supported. Is there anyway we can
cache the TCP query??
Regards
Harish Shetty
On Wed, May 9, 2018 at 1:42
On Tue, May 08, 2018 at 11:16:51PM +0200, Dominik wrote:
> On 08.05.2018 22:17, Simon Kelley wrote:
> > From: Dominik Derigs , Date: Tue, 8 May 2018 18:44:41 +0200
> >> [PATCH] Remove upper limit of 10,000 for cache size.
> >>
> >> We should allow users to set any (maximum) cache