> Have you tried an rndc flush? You can also dump the contents of the
> cache to find the (approximate) size of the cache. If related to cache,
> you can tweak parameters to cache, most namely max-cache-size. IIRC,
> the cache doesn't have a size limit by default.
>
> /Tim
>
I did an rndc d
It might have something to do with the number of CPUs that named detects
when it starts, which (by default) drives how many listening tasks it
starts per listening interface.
BIND 9.10 changed the defaults slightly, but you can also control how
many listening tasks per interface using the -U optio
Hi Cathy,
I think you may be correct. I am running these in cloud hosted VMs. I found
that the problem is difficult to reproduce with a 2 core instance. With a 4
core instance it only happens with reload/reconfig and with 8 cores it
doesn't get past start up. From the VM's perspective, I only have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
dig newsrss.bbc.net.uk a @212.58.240.162 +nodnssec +norecur
;; ->>HEADER<<- opcode: QUERY, status: FORMERR, id: 24230
;; flags: qr aa ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: EDNS query returned status FORMERR - retry with '+no
e-height:17px;font-family:Calibri=
> > > ,Sans-Serif;font-size:11pt"> > style=3D"background-color:inherit">Jul 15=
> > > 19:20:57 > style=3D"background-color:inherit"
Yes. This is what happens when you try to re-write the query to
send a request but use the query length rather that the response
length to send the reply.
Mark
In message <1405715388.29526.25.ca...@ns.five-ten-sg.com>, Carl Byington writes
:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
6 matches
Mail list logo