From: Robert Bradley <robert.bradley1@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] DNSSEC failure for *.cloudflare.com via dnsmasq?
Date: Sat, 12 Apr 2014 13:24:35 +0100 [thread overview]
Message-ID: <53493083.40808@gmail.com> (raw)
In-Reply-To: <874n1ykb68.fsf@alrua-x1.kau.toke.dk>
[-- Attachment #1: Type: text/plain, Size: 1071 bytes --]
On 12/04/2014 13:02, Toke Høiland-Jørgensen wrote:
> Robert Bradley <robert.bradley1@gmail.com> writes:
>
>> That seems to suggest that it's the DS queries that are failing and
>> that this is probably not a dnsmasq bug. Trying Verisign's DNSSEC
>> debugger (http://dnssec-debugger.verisignlabs.com/blog.cloudflare.com)
>> seems to suggest that their nameservers refuse requests for DNSKEY
>> records.
> I seem to have no problems resolving either cloudfare.com or
> cloudfare.net with dnssec validation enabled. But then I might have a
> different view of their DNS infrastructure; I'm in Sweden...
>
> You can try running dig with +dnssec +trace to see where in the chain
> things go wrong...
>
> -Toke
Using +dnssec +trace returns no errors, but that ends up bypassing both
Google's DNS servers and dnsmasq in favour of going directly to the DNS
root. It looks like there is some issue with 8.8.8.8 and 8.8.4.4
disliking that particular domain (at least from a UK point of view), but
I am unable to see what it is.
--
Robert Bradley
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]
next prev parent reply other threads:[~2014-04-12 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-12 11:06 Robert Bradley
2014-04-12 11:11 ` Toke Høiland-Jørgensen
2014-04-12 11:53 ` Robert Bradley
2014-04-12 12:02 ` Toke Høiland-Jørgensen
2014-04-12 12:24 ` Robert Bradley [this message]
2014-04-12 19:06 ` Dave Taht
2014-04-12 19:07 ` Michael Richardson
2014-04-12 20:30 ` Robert Bradley
2014-04-12 20:54 ` Michael Richardson
2014-04-12 21:27 ` Robert Bradley
2014-04-12 11:13 ` Robert Bradley
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=53493083.40808@gmail.com \
--to=robert.bradley1@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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