Greg Choules wrote:
> Point taken. Unique does not necessarily mean non-existent and *something*
> will end up in cache. So restricting your max-cache-size would seem to be
> the thing for you. If it were my server, I would monitor just how much RAM
> is getting used in total and adjust
Point taken. Unique does not necessarily mean non-existent and *something*
will end up in cache. So restricting your max-cache-size would seem to be
the thing for you. If it were my server, I would monitor just how much RAM
is getting used in total and adjust max-cache-size to allow BIND to use as
Greg Choules wrote:
> Since the queries are unique the responses should be NXDOMAIN
Well, _some_ of them will be NXDOMAIN, many others
will be NOERROR or NODATA etc., no? But yes, they all
ended up contributing to the cache growing, and it
seems that 90% of physical memory all in use by bind
Hi Jan.
Since the queries are unique the responses should be NXDOMAIN, which *will*
be cached and therefore consume memory. This is why I was curious what you
are hitting it with.
You can see these cache entries if you dump it using "rndc dump -cache".
This produces a file (by default) called
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
https://www.five-ten-sg.com/mapper/bind contains links to the source
rpm, and build instructions. This .src.rpm contains a .tar.gz file with
the ARM documentation, so the rpm rebuild process does not need sphinx-
build and associated dependencies.
On 14/02/23 05:39, adrien sipasseuth wrote:
"You configure parental agents and named will check which DS’s are
published. Named won’t complete the
roll until it knows the new DS is published."
=> what is parental agent ? i don't find this term in Bind
documentation. From what I understand,
6 matches
Mail list logo