DLV records for TLD's signed using RASSHA256 (and RSASHA512)
will be added DLV.ISC.ORG in the next few days.
BIND 9.6.0 and BIND 9.6.0-P1 do not correctly handle these
records and it is recommended that you upgrade to BIND 9.6.1
or later
On Dec 15 2009, Evan Hunt wrote:
(Doug Barton wrote)
BIND 9.6.2 is in the b1 phase atm, which means that there is plenty
of time to get SHA2 in there and get the release out before a signed
root goes live. I encourage the folks at ISC to do so, and if you
agree I encourage you to make your
We hear you. Expect a decision in the next few days.
So, has the decision been made?
[I am tentatively planning on going to 9.7 in production round about Easter,
in good time for the RSASHA256-signed root zone in July, but it would be
nice to have a fall-back option.]
I'm sorry, I
On Dec 15 2009, Doug Barton wrote:
While this reminder is timely and helpful, more welcome would be the
news that BIND 9.6.2 is going to have actual support for
RSASHA{256|512}. My cursory reading of the 9.6.2b1 code does not seem
to indicate that it does, although I would be happy to be proven
On Mon, Dec 14, 2009 at 08:05:40PM -0800,
Doug Barton do...@dougbarton.us wrote
a message of 44 lines which said:
While this reminder is timely and helpful, more welcome would be the
news that BIND 9.6.2 is going to have actual support for
RSASHA{256|512}.
No, it won't. Migrating to =
Chris Thompson wrote:
(Evan Hunt)
Adding SHA-2 to 9.6.x would violate our policy of making major
functional changes only in major releases, so I don't expect we'll
do that. Given the odd circumstances you mentioned, I won't say for
certain that we won't--but I doubt it.
9.7.0 is going to
Evan Hunt wrote:
BIND 9.6.2 is in the b1 phase atm, which means that there is plenty
of time to get SHA2 in there and get the release out before a signed
root goes live. I encourage the folks at ISC to do so, and if you
agree I encourage you to make your voice heard.
We hear you.
That's
BIND 9.6.2 is in the b1 phase atm, which means that there is plenty
of time to get SHA2 in there and get the release out before a signed
root goes live. I encourage the folks at ISC to do so, and if you
agree I encourage you to make your voice heard.
We hear you. Expect a decision in the
In message prayer.1.3.2.0912151543550.32...@hermes-1.csi.cam.ac.uk, Chris Tho
mpson writes:
(But it's not too obvious to me that adding support for a new signing
algorithm should necessarily be considered a major functional change.)
If it was *just* adding a new signing algorithm then yes it
://SupersetSolutions.com/
Mark Andrews wrote:
With upcoming deployment of RSASHA256 to sign the root zone, ISC
would like to remind BIND 9.6.0 and BIND 9.6.0-P1 users that use
DLV, but have not yet upgraded, that they will need to upgrade to
a more recent version of BIND 9.6.x as BIND 9.6.0 and BIND 9.6.0-P1
Carl Fretwell wrote:
Hi Everyone
I have installed BIND 9.6.0-P1 on a Windows Server 2003 x64 system but
when I come to start the âISC BINDâ service I always get a 1067 error
which I read somewhere was due to permissions so made sure the user
account password etc was correct still
Hi Everyone
I have installed BIND 9.6.0-P1 on a Windows Server 2003 x64 system but when I
come to start the ISC BIND service I always get a 1067 error which I read
somewhere was due to permissions so made sure the user account password etc was
correct still didn't fix the issue.
Sometimes
In message p05200f70c5d52b51d...@[130.102.20.138], Ray Phillips writes:
I've built bind 9.6.0-P1 on NetBSD/i386 machines (versions 3.1, 4.0,
4.0.1 and 5.0_RC2) and discovered that nsupdate dumps core on the 4.x
ones.
The build process was just:
% sh -c './configure --disable-threads
I've built bind 9.6.0-P1 on NetBSD/i386 machines (versions 3.1, 4.0,
4.0.1 and 5.0_RC2) and discovered that nsupdate dumps core on the 4.x
ones.
I just built and installed bind-9.6.0-P1 on NetBSD/i386 4.0 and nsupdate
doesn't crash for me. (Built with default pthread and also linked
(mctx=0x817, ectx=0x8184000, eflags=0)
at dst_api.c:183
#12 0x0804c43a in main (argc=Cannot access memory at address 0x2
) at nsupdate.c:772
(gdb) quit
%
I just built and installed bind-9.6.0-P1 on NetBSD/i386 4.0 and nsupdate
doesn't crash for me. (Built with default pthread and also
In message p05200f72c5d61071b...@[130.102.20.138], Ray Phillips writes:
You need to call gdb correctly.
gdb /usr/local/bin/nsupdate nsupdate.core
Thanks Mark.
Sorry, I (obviously) don't have much of a clue about using gdb.
Looks like you have hit this bug.
2547.
Recently I upgraded my bind machine to a new windows 2008 server web edition
32 bit with 2 E5420 quad core CPU's.
The server is configured with about 7000 master zone files.
Since the upgrade, BIND hangs every 5-10 hours.
I checked the logs and I saw these lines on the default log:
Kobi Shachar wrote:
Recently I upgraded my bind machine to a new windows 2008 server web
edition 32 bit with 2 E5420 quad core CPU's.
The server is configured with about 7000 master zone files.
Since the upgrade, BIND hangs every 5-10 hours.
I checked the logs and I saw these lines
, January 26, 2009 4:49 AM
To: Kobi Shachar
Cc: bind-users@lists.isc.org
Subject: Re: BIND 9.6.0-P1 on windows server 2008 32 bit hangs
Kobi Shachar wrote:
Recently I upgraded my bind machine to a new windows 2008 server web
edition 32 bit with 2 E5420 quad core CPU's.
The server is configured
19 matches
Mail list logo
