From: James Cloos <cloos@jhcloos.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: dnsmasq-discuss <Dnsmasq-discuss@lists.thekelleys.org.uk>,
"cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss] test-ipv6.com vs dnssec
Date: Mon, 28 Apr 2014 15:57:43 -0400 [thread overview]
Message-ID: <m3lhupdy5r.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <CAA93jw66ZC14u88jOgFOhbj-QQgNVfZSZnxWTTRBVLNSEx8ZAQ@mail.gmail.com> (Dave Taht's message of "Mon, 28 Apr 2014 12:07:06 -0700")
>>>>> "DT" == Dave Taht <dave.taht@gmail.com> writes:
DT> As one example of a registrar not with the program, name.com
DT> (registrar for bufferbloat.net) does not allow for ds records to
DT> come from it, so that domain can't be fully signed.
DT> So it sounds to me as if negative proofs are not possible with
DT> registrars that lack this support?
No. Signed parent zones (like com, net, org) always provide either a
signed DS record if it exists or proof of non-existance.
Try doing:
dig @i.gtld-servers.net. bufferbloat.net ds +dnssec
The two nsec3 records (each signed by an rrsig record) prove that there
is no DS record in net. with the name bufferbloat.net.
Compare that with what you get asking for ns records:
That replies with the two ns records, as well as the proof that the DS
records do not exist.
Now, try with a zone which is signed:
dig @i.gtld-servers.net. jhcloos.net ns +dnssec
dig @i.gtld-servers.net. jhcloos.net ds +dnssec
The first returns both the ns and ds records, with an rrsig over the ds
records (returned in the authority section); the latter returns the
signed ds records in the answer section and net's own signed ns set in
the authority section.
Given that some zones have nameservers which fail to respond if they do
not like or understand the query, it seems that only root-down verifi-
cation can work. Unless I'm missing something....
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2014-04-28 20:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-25 17:39 [Cerowrt-devel] " Dave Taht
2014-04-25 18:01 ` Jim Gettys
2014-04-25 18:45 ` James Cloos
2014-04-25 18:49 ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2014-04-25 19:43 ` Török Edwin
2014-04-25 19:48 ` Török Edwin
2014-04-28 19:07 ` Dave Taht
2014-04-28 19:57 ` James Cloos [this message]
2014-04-28 20:17 ` Török Edwin
2014-04-30 21:44 ` James Cloos
2014-04-25 19:24 ` [Cerowrt-devel] " Török Edwin
2014-04-25 19:42 ` Dave Taht
2014-04-26 19:41 ` Sebastian Moeller
2014-04-27 16:15 ` Dave Taht
2014-04-27 19:49 ` Sebastian Moeller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3lhupdy5r.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=Dnsmasq-discuss@lists.thekelleys.org.uk \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox