From: Dave Taht <dave.taht@gmail.com>
To: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: [Cerowrt-devel] Fwd: [Dnsmasq-discuss] dnsmasq-2.73rc2
Date: Sun, 29 Mar 2015 16:57:01 -0700 [thread overview]
Message-ID: <CAA93jw7awPjPPgFbeRSTQgHP6_ubD4RYdLPx5-a5gJTbjytcnQ@mail.gmail.com> (raw)
In-Reply-To: <55186E6D.4020404@thekelleys.org.uk>
Isn't it great to so help fix bugs at scale?
---------- Forwarded message ----------
From: Simon Kelley <simon@thekelleys.org.uk>
Date: Sun, Mar 29, 2015 at 2:28 PM
Subject: [Dnsmasq-discuss] dnsmasq-2.73rc2
To: dnsmasq-discuss <Dnsmasq-discuss@lists.thekelleys.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For those interested in DNSSEC, I just pushed 2.73rc2, which has a few
fixes for DNSSEC edge cases that have come from a couple of days of
systematic testing.
It's worth noting that the Google Public DNS currently has a problem
returning the DS record for in-addr.arpa. This causes every reverse
lookup through dnsmasq to fail when DNSSEC validation is on and
dnsmasq is using Google as upstream. Google are aware, have
acknowledged the problem, and expect a fix in the next week or so.
Ain't DNSSEC fun?
Cheers,
Simon.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iEYEARECAAYFAlUYbm0ACgkQKPyGmiibgrcXlwCgkKrZjCIszzjfYhyHENp6imgt
OagAn2PRS0LPKpw9zYujwJm4YvBO7Gl7
=qQlY
-----END PGP SIGNATURE-----
_______________________________________________
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
parent reply other threads:[~2015-03-29 23:57 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <55186E6D.4020404@thekelleys.org.uk>]
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=CAA93jw7awPjPPgFbeRSTQgHP6_ubD4RYdLPx5-a5gJTbjytcnQ@mail.gmail.com \
--to=dave.taht@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