From: Robert Bradley <robert.bradley1@gmail.com>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] [Dnsmasq-discuss] more dnssec failures
Date: Wed, 23 Apr 2014 18:16:12 +0100 [thread overview]
Message-ID: <5357F55C.1030500@gmail.com> (raw)
In-Reply-To: <5357EDE7.2000409@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
On 23/04/2014 17:44, Robert Bradley wrote:
> 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...
Digging into this further, it looks like the issue occurs for domain
names where an A record exists but a DS record does not. In the case
where the A/AAAA record is non-existent, (e.g.
dscc.akamaiedge.net.0.1.cn.akamaiedge.net. instead of e3191.<...> or
non-existent.cloudflare.com), you get the expected NOERROR or NXDOMAIN
response. It would be worth testing this on a non-dual-stacked host or
a subdomain without related A/AAAA records too.
--
Robert Bradley
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2014-04-23 17:16 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
2014-04-23 17:16 ` Robert Bradley [this message]
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=5357F55C.1030500@gmail.com \
--to=robert.bradley1@gmail.com \
--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