Hi,
After reinitialising the inline-signing process (for example by
removing the journal files or redeploying the master server) the
freshly signed zone's serial number will usually be behind the
authoritative version on the slaves causing transfers to fail
possibly leading to expired
...
Heh thanks, yeah...initially I was erring on the side of caution and using
9.9.x because it's served us well (~20k recursive clients without any
significant problems). Meanwhile we've been keeping a close eye on
community comments, and to be honest opinions wax and wane. Just as I
On Monday 13/10/2014 at 1:32 pm, sch...@adi.com (Thomas Schulz) wrote:
...
Heh thanks, yeah...initially I was erring on the side of caution and
using
9.9.x because it's served us well (~20k recursive clients without any
significant problems). Meanwhile we've been keeping a close eye
On Mon, 13 Oct 2014, Thomas Schulz wrote:
I restarted bind 9.9.6 with a max-cache-size of 30M. We have 3 views.
The inital process size was 36 MB. The process grew to 184 MB. It grew
to 596 MB without the max-cache-size being set and was still growing
when I restarted it. BUT when I now do
Hi Thomas
On Mon, Oct 13, 2014 at 02:31:37PM -0400, Thomas Schulz wrote:
I restarted bind 9.9.6 with a max-cache-size of 30M. We have 3 views.
The inital process size was 36 MB. The process grew to 184 MB. It grew
to 596 MB without the max-cache-size being set and was still growing
when I
5 matches
Mail list logo