I'll be reporting this to bind-bugs, but I thought I would mention it here
in case others can confirm the effect.
Our two main ecursive nameservers used DNSSEC validation via dlv.isc.org.
In the past we have had suspicions that there are glitches when new entries
appear in the DLV zone. For
At Wed, 10 Mar 2010 14:45:48 +0100,
Dangl, Thomas thomas.t.da...@siemens.com wrote:
in Bind 9.6.2 the zone statistics looked like that:
Now with Bind9.7.0 it only covers
zone
name4.3.2.1.e164.arpa/IN/name
rdataclassIN/rdataclass
serial8/serial
Hi,
I have two servers each running bind 9.7.0. I have TSIG setup on the
servers. I upgraded the hardware on the primary server. The IPs and the
config remained the same.
I upgrade BIND from 9.4.3-P3 to 9.7.0 at the same time on the primary.
Prior to the hardware/BIND upgrade TSIG worked good.
In message off7240f74.a2c76455-on062576f1.0068f1ea-062576f1.006c5...@sasktel.s
k.ca, Greg Kuechle writes:
Hi,
I have two servers each running bind 9.7.0. I have TSIG setup on the
servers. I upgraded the hardware on the primary server. The IPs and the
config remained the same.
I upgrade
I have 40+ domains, how to improve the startup speed of named。
The first startup took more than 3 hours.
named version:bind-9.7.0-P1
To build with --enable-threads
Cent OS 5.4(64Bit)
Intel(R) Xeon(R) CPU E5405 @ 2.00GHz(4*2 cores)
Memory: 16G
5 matches
Mail list logo