I have the same problem in Ubuntu 10.04.3 server and Scientific Linux 6.
The solution is key -r /dev/urandom. The result is something like this:
rndc-confgen -b 512 -r /dev/urandom /etc/rndc.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Changed in: bind9 (Ubuntu)
Assignee: (unassigned) = andrew667 (andrei-yurevich)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in Ubuntu.
https://bugs.launchpad.net/bugs/697609
Title:
rndc-confgen does nothing
To
I suspect that it is waiting on /dev/random to provide it with data, and
that:
rndc-confgen -b 256 -c /etc/named/rndc.key -r /dev/urandom
would give you a result quickly.
I'm marking this 'Triaged' as I agree with the suggestion of a message
stating its waiting on random data.
** Changed in:
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
https://bugs.launchpad.net/bugs/697609
Title:
rndc-confgen does nothing
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or
After about an hour it generated output!
Maybe we shall have some message it is working on key generation
:-(
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to bind9 in ubuntu.
https://bugs.launchpad.net/bugs/697609
Title:
