From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Cc: Dnsmasq-discuss@lists.thekelleys.org.uk
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss] more dnssec failures
Date: Wed, 23 Apr 2014 17:44:23 +0100 [thread overview]
Message-ID: <5357EDE7.2000409@gmail.com> (raw)
In-Reply-To: <5357E336.6070406@thekelleys.org.uk>
[-- Attachment #1: Type: text/plain, Size: 2146 bytes --]
On 23/04/2014 16:58, Simon Kelley wrote:
> On 23/04/14 16:42, Dave Taht wrote:
>> I will argue that a better place to report dnssec validation
>> errors is the dnsmasq list.
>>
>> On Wed, Apr 23, 2014 at 8:31 AM, Aaron Wood <woody77@gmail.com> wrote:
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: query[A]
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net from 172.30.42.99
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: forwarded
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net to 8.8.8.8
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: dnssec-query[DS]
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net to 8.8.8.8
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: forwarded
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net to 8.8.4.4
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: forwarded
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net to 8.8.8.8
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: reply
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net is BOGUS DS
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: validation result is
>>> BOGUS
>>> Wed Apr 23 15:13:05 2014 daemon.info dnsmasq[29719]: reply
>>> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net is 2.20.28.186
>>>
>>> This one validates via verisign, however.
>>>
> Something strange in that domain. Turning off DNSSEC with the
> checking-disabled bit, the original A-record query is OK
>
>
> ; <<>> DiG 9.8.1-P1 <<>> +cd @8.8.8.8 a
> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net
<snip rest of NOERROR response>
>
> But a query for DS on the same domain, which is what dnsmasq does next,
> returns SERVFAIL, _even_with_ checking disabled.
>
> ; <<>> DiG 9.8.1-P1 <<>> +cd @8.8.8.8 ds
> e3191.dscc.akamaiedge.net.0.1.cn.akamaiedge.net
<snip SERVFAIL response>
This looks identical to the *.cloudflare.com issue I had last week. In
both cases, using Level 3's 4.2.2.2 instead of Google DNS works fine,
and 8.8.8.8 returns SERVFAIL for DS lookups. This looks like a bug in
Google's DNS servers as opposed to dnsmasq...
--
Robert Bradley
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2014-04-23 16:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-23 15:31 [Cerowrt-devel] " Aaron Wood
2014-04-23 15:42 ` Dave Taht
2014-04-23 15:58 ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2014-04-23 16:44 ` Robert Bradley [this message]
2014-04-23 17:16 ` Robert Bradley
2014-04-23 17:28 ` Robert Bradley
2014-04-23 17:18 ` Aaron Wood
2014-04-23 17:29 ` Dave Taht
2014-04-23 19:04 ` Simon Kelley
2014-04-24 10:49 ` Aaron Wood
2014-04-24 11:27 ` Simon Kelley
2014-04-24 12:33 ` Aaron Wood
[not found] ` <CALQXh-O4puZOB710+R2CcY3AEqTZhAJvU8YFsjjH3_xK1CdXvA@mail.gmail.com>
2014-04-24 16:03 ` Dave Taht
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=5357EDE7.2000409@gmail.com \
--to=robert.bradley1@gmail.com \
--cc=Dnsmasq-discuss@lists.thekelleys.org.uk \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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