In message <20090624211854.a3be222...@thrintun.hactrn.net>, Rob Austein writes:
> At Wed, 24 Jun 2009 18:23:52 +, Evan Hunt wrote:
> >
> > On Wed, Jun 24, 2009 at 05:45:33PM +0200, holger.zule...@arcor.net wrote:
> > > I have some issues with dnssec-signzone under BIND 9.7.0a1.
> > >
> > > I
In message , Chris Buxton
writes:
> On Jun 24, 2009, at 1:54 AM, Scott Haneda wrote:
> > On Jun 23, 2009, at 11:57 PM, Chris Buxton wrote:
> >> On Jun 23, 2009, at 3:16 PM, Scott Haneda wrote:
> >>> Good observation. This is a long standing issue that I assumed
> >>> was solved. Named on OS X
At Wed, 24 Jun 2009 18:23:52 +, Evan Hunt wrote:
>
> On Wed, Jun 24, 2009 at 05:45:33PM +0200, holger.zule...@arcor.net wrote:
> > I have some issues with dnssec-signzone under BIND 9.7.0a1.
> >
> > I'm using different algorithms for key- and zone signing keys.
>
> You can use multiple algor
On Wed, Jun 24, 2009 at 05:45:33PM +0200, holger.zule...@arcor.net wrote:
> I have some issues with dnssec-signzone under BIND 9.7.0a1.
>
> I'm using different algorithms for key- and zone signing keys.
That's a problem.
> Does it mean that it is no longer possible to use different key algorithm
On Jun 24, 2009, at 1:54 AM, Scott Haneda wrote:
On Jun 23, 2009, at 11:57 PM, Chris Buxton wrote:
On Jun 23, 2009, at 3:16 PM, Scott Haneda wrote:
Good observation. This is a long standing issue that I assumed
was solved. Named on OS X will go deaf on port 53 tcp for some
reason. I just
At Wed, 24 Jun 2009 10:13:51 +0400,
Dmitry Rybin wrote:
> > new experimental feature just for that purpose:
> Is this feature going to be back ported to 9.4 and 9.5 releases as well?
> >>> For 9.5, yes. For 9.4, not according to the current plan.
> >> named[87071]: 22-Jun-2009 13:18:23.
Thanks. I obviously missed that part of the rfc.
--
Jack Tavares
From: Chris Thompson [c...@hermes.cam.ac.uk] On Behalf Of Chris Thompson
[c...@cam.ac.uk]
Sent: Wednesday, June 24, 2009 18:44
To: Jack Tavares
Cc: Bind Users Mailing List
Subject: RE: can't
On Sun, 21 Jun 2009, R Dicaire wrote:
> Hi folks, bind 9.6.1...I'm looking in the ARM but I dont see a logging
> category specific to control channel communications.
> In syslog I have (generated by an mrtg script):
>
> named[7837]: received control channel command 'stats'
>
> What category does
I have some issues with dnssec-signzone under BIND 9.7.0a1.
I'm using different algorithms for key- and zone signing keys.
This is the list of currently used keys:
$ dnssec-zkt .
Keyname Tag Typ Sta Algorit Generation Time
sub.example.de. 56595 KSK
On Jun 24 2009, Jack Tavares wrote:
a correction:
my dig command is
dig @127.0.0.1 -t RRSIG 4PPH7Q8R02M0AD8MLJPS0UEH2AB9KFJL.test.net
and I still get NXDOMAIN
NSEC3 records (and their associated RRSIG records) are, in a sense, not
properly part of the zone. RFC 5155 section 7,2,8 "Respondi
> > Does anybody know if (or when) BIND supports HIP (RFC5205)
> > resource records ?
>
>It's in BIND 9.7. BIND 9.7.0a1 is in the process of being prepared.
>
> 2565. [func] Add support for HIP record. Includes new
functions
> dns_rdata_hip_first(), dns_r
a correction:
my dig command is
dig @127.0.0.1 -t RRSIG 4PPH7Q8R02M0AD8MLJPS0UEH2AB9KFJL.test.net
and I still get NXDOMAIN
--
Jack Tavares
AIM: jacktavares
SKYPE: jackandkaddee
Reminder: I am at GMT+2, 10 hours AHEAD of Seattle.
My workweek is Sunday-Thursday.
Email sent to me Thursday afternoo
When I query my test zone I get RRSIG records that cover NSEC3
and all the NSEC3 records etc like so:
dig axfr @127.0.0.1 test.net.
; <<>> DiG 9.6.1 <<>> axfr @127.0.0.1 test.net.
; (1 server found)
;; global options: +cmd
test.net. 500 IN SOA d62.test.net.
hostmaster.
On Jun 23, 2009, at 11:57 PM, Chris Buxton wrote:
On Jun 23, 2009, at 3:16 PM, Scott Haneda wrote:
Good observation. This is a long standing issue that I assumed was
solved. Named on OS X will go deaf on port 53 tcp for some
reason. I just kicked it, and now I can tcp dig it.
$dig +tcp
14 matches
Mail list logo
