On Sat, 2012-04-21 at 20:28 -0400, Bill Owens wrote:
On Sun, Apr 22, 2012 at 01:11:55AM +0100, Damian Myerscough wrote:
Hello,
I was setting up BIND DNSSEC and when I issue the following command the
process never finishes.
dnssec-keygen -a RSASHA1 -b 1024 -n ZONE example.com
I was setting up BIND DNSSEC and when I issue the following command the
process never finishes.
dnssec-keygen -a RSASHA1 -b 1024 -n ZONE example.com
Take a look at the Entropy Key (http://www.entropykey.co.uk/). See also a
discussion
On 4/20/2012 10:55 AM, John Wingenbach wrote:
I've noticed the support in ARM for specifying both the forward and
forwarders configuration in a zone stanza for slave zones. What
is the purpose and value of specifying such? It seems contradictory
and confusing.
Yes, it is confusing IMO, but
Thanks a lot, I have now resolved this issue. However, I was following
the DNSSEC in 6 minutes guide [1]
for learning purposes and I have followed all the steps up to you are now
serving DNSSEC signed zones.
However, I seem to be getting the following errors
Apr 22 15:22:43 darkstar
On Sun, 2012-04-22 at 16:31 +0100, Damian Myerscough wrote:
Thanks a lot, I have now resolved this issue. However, I was following
the DNSSEC in 6 minutes guide [1]
for learning purposes and I have followed all the steps up to you are
now serving DNSSEC signed zones.
Reading the presentation
Thanks for your help, I noticed a small regex which modified my
configuration file thus causing errors.
On 22 April 2012 17:03, Mark Elkins m...@posix.co.za wrote:
On Sun, 2012-04-22 at 16:31 +0100, Damian Myerscough wrote:
Thanks a lot, I have now resolved this issue. However, I was
I am a Wisp admin and I have just configured a couple of new Bind9 servers.
They will resolve using dig google.com @9x.1xx.104.14
I am having some trouble getting them to answer themselves on 127.0.0.1
for example:
[root@ns4 named]# dig google.com @127.0.0.1 +trace
; DiG
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 04/22/2012 10:05 PM, David Milholen wrote:
listen-on {
9x.1xx.104.14;
};
Perhaps add 127.0.0.1; into the listen on clause.
- --
Larry Brower, CCENT
Fedora Ambassador - North America
Fedora Quality Assurance
You set a listen-on that does not include 127.0.0.1.
On Apr 22, 2012 11:08 PM, David Milholen dmilho...@wletc.com wrote:
I am a Wisp admin and I have just configured a couple of new Bind9
servers.
They will resolve using dig google.com @9x.1xx.104.14
I am having some trouble getting them to
9 matches
Mail list logo
