From: Dave Taht <dave.taht@gmail.com>
To: Robert Bradley <robert.bradley1@gmail.com>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] DNSSEC failure for *.cloudflare.com via dnsmasq?
Date: Sat, 12 Apr 2014 12:06:16 -0700 [thread overview]
Message-ID: <CAA93jw7E4mCcAk-c0MjEwtAQf7ibDJiABEEz1GaVu-p48a9MCA@mail.gmail.com> (raw)
In-Reply-To: <53493083.40808@gmail.com>
I tweeted this thread to cloudflare.
On Sat, Apr 12, 2014 at 5:24 AM, Robert Bradley
<robert.bradley1@gmail.com> wrote:
> 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
>
>
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
next prev parent reply other threads:[~2014-04-12 19:06 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
2014-04-12 19:06 ` Dave Taht [this message]
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=CAA93jw7E4mCcAk-c0MjEwtAQf7ibDJiABEEz1GaVu-p48a9MCA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=robert.bradley1@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