On Mar 7, 2012, at 6:23 PM, Mark Andrews wrote:
> Compile in +sigchase support and give it a root key.
Evan Hunt told us (regarding +sigchase) "in its current state it's terrible and
you really shouldn't use it."
I'm not sure who to believe.
> TCP has *never* been optional for DNS. Unfortunat
In message <7b71a06b-ca32-4e96-9ae0-0c0e29eb1...@yahoo-inc.com>, "Mark K. Petti
t" writes:
> That's a little more output, but when you try it, notice that there's no =
> "dig org. DNSKEY" in the output, which is the query that was hanging in =
> my case.
Compile in +sigchase support and give it a
On Tue, Mar 06, 2012 at 07:37:31PM -0800, Mark K. Pettit wrote:
> Please add something to "dig" that replicates the behavior of BIND as
> closely as possible with regards to the many queries it issues as part of
> a DNSSEC-validing resolution.
There's "dig +sigchase", but a) you have to enable it
That's a little more output, but when you try it, notice that there's no "dig
org. DNSKEY" in the output, which is the query that was hanging in my case.
On Mar 6, 2012, at 9:10 PM, Mark Andrews wrote:
>
> dig +trace +qr +comment +question
>
> --
> Mark Andrews, ISC
> 1 Seymour St., Dun
dig +trace +qr +comment +question
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubs
Hi, fellow BIND users.
The other day I was attempting to diagnose a problem on a recursive resolving
name server. I had just enabled DNSSEC Validation, and certain digs (such as
"www.isc.org", "www.dnssec-failed.org") were failing. Even queries to
non-signed domains such my own personal domai
6 matches
Mail list logo
