Description of problem:
bind fails to start with the following error:
view.c:1196: REQUIRE(keyp != ((void *)0) && *keyp == ((void *)0))
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Try to start bind after having configured tsig keys
bind fails to start
bind should start and initiate a transfer if necessary
Apparently, this is know, but it is critical for anyone who uses keys to
transfer data between master/slave servers.
Here is a link to what I found on this:
Yes, I know about this problem but I think we could wait to 9.4.2 when noone
reports it. Update will be avaliable very soon (also on
Thanks for the update. When you say "we could wait"... How long do you
anticipate? I have a backup server in a remote location that depends on these
updates from the master. Now that network is non-functional in terms of name
If the wait will be more than a day, what are the alternatives that I can
implement for zone transfers in the mean time? Would switching to IP based
Also, if I needed to rool-my-own from the src rpm, would I need to specify any
modifyers to the rpmbuild command, or could I just patch using the patch
supplied in the above link and do an rpmbuild without modifiers/conditionals to
mimic the default fedora install of bind?
Again, thanks for your help.
With "we could wait" I though when noone reports this problem that means that
nobody uses TSIGs so I don't have to backport patch :) But now, when report
exists I'm going to release it. Update will be avaliable tomorrow
Thanks a lot. How do people do transfers then? Am I using an old method or
People often think that Internet is security so do transfers without any
protection because they don't want waste time with correct setup :) Your method
is recommended and modern
thanks. glad to hear i'm doing something right :) anyway, your .8 release works
(i rolled my own rpm) so test #1 is good! i appreciate the quick replies.
bind-9.4.1-8.P1.fc7 has been pushed to the Fedora 7 stable repository. If problems still persist, please make note of it in this bug report.