From: David Personette <dperson@gmail.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] DNSSEC and www.ietf.org
Date: Mon, 30 Mar 2015 12:19:02 -0400 [thread overview]
Message-ID: <CAMybZqyuxX8yRt52Zms75YVOmJoC2fnGEwRvgd+uD8Vw4V_BJg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4L-EgiUWQ5K8iPi0aFAmYYfU9bNYiS_0h6o2DrrqfrVQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Dave,
Sorry to be pedantic, but did you mean:
A) You did have the issue with older versions, and you still see that issue
with those old versions.
B) You did have the issue with older versions, and you also have it with
the current beta version of dnsmasq.
Thanks.
P.S. I'd had several weeks of issues with DNSsec enabled (due to the Google
issue), and disabled it about a week or two ago.
--
David P.
On Mon, Mar 30, 2015 at 11:58 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I have trouble accessing ietf.org, also, with older versions of
> dnsmasq + dnssec, presently.
>
> On Mon, Mar 30, 2015 at 8:52 AM, Marc Petit-Huguenin
> <marc@petit-huguenin.org> wrote:
> > Am I the only one who cannot access www.ietf.org since Cloudflare
> enabled DNSSEC? (with dnsmasq-full 2.73-3)
> >
> > Thanks.
> >
> > --
> > Marc Petit-Huguenin
> > Email: marc@petit-huguenin.org
> > Blog: http://blog.marc.petit-huguenin.org
> > Profile: http://www.linkedin.com/in/petithug
> >
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
>
> --
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
>
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
[-- Attachment #2: Type: text/html, Size: 3026 bytes --]
next prev parent reply other threads:[~2015-03-30 16:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-30 15:52 Marc Petit-Huguenin
2015-03-30 15:58 ` Dave Taht
2015-03-30 16:19 ` David Personette [this message]
2015-03-30 17:49 ` [Cerowrt-devel] [Dnsmasq-discuss] " Simon Kelley
2015-03-30 18:17 ` Marc Petit-Huguenin
2015-03-30 18:42 ` Dave Taht
2015-04-11 15:03 ` Marc Petit-Huguenin
2015-04-11 16:32 ` Kevin Darbyshire-Bryant
2015-04-11 16:49 ` Dave Taht
2015-04-11 19:13 ` Kevin Darbyshire-Bryant
2015-04-13 14:02 ` Marc Petit-Huguenin
2015-04-11 16:38 ` 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=CAMybZqyuxX8yRt52Zms75YVOmJoC2fnGEwRvgd+uD8Vw4V_BJg@mail.gmail.com \
--to=dperson@gmail.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