From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Full blown DNSSEC by default?
Date: Sun, 13 Apr 2014 07:57:18 -0700 [thread overview]
Message-ID: <CAA93jw5JoQWL5Grq+qH1ypu-QzTLdKKnJkgxoa3iaoKUk-G5gg@mail.gmail.com> (raw)
In-Reply-To: <1c739791-2058-4267-bc41-789496d74faf@email.android.com>
On Sun, Apr 13, 2014 at 3:05 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
>> Is there a "D"?
>
> Running a full resolver in cerowrt? I've been running a dnssec-enabled bind for some time on my boxes (prior to dnssec support in dnsmasq).
I had done quite a few optimizations to make running a full blown
bind9 resolver at home pretty performant (caching the roots, for
example). I also liked being able to do full split dns, etc.
But: I got fed up with doing bind for a variety of reasons:
A) 4 CERT alerts in a year, including a couple nasty ones
B) Too hard to configure even for a wizard
C) Too hard to configure via a web interface
D) People blocking the roots
E) Would run out of flash easily with the jnl file
So I pursued finding something (e.g. dnsmasq) that was smaller,
more integrated, easier to configure, and easy on ram and flash.
so that's dnsmasq today. It seems more plausible to continue to
improve dnsmasq than it is to dumb down bind.
I do not mind continuing to support and improve optional bind and
unbound support for those that want to use them.
> -Toke
>
>
--
Dave Täht
NSFW: https://w2.eff.org/Censorship/Internet_censorship_bills/russell_0296_indecent.article
next prev parent reply other threads:[~2014-04-13 14:57 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 4:26 Dave Taht
2014-04-13 7:51 ` Török Edwin
2014-04-13 15:04 ` Dave Taht
2014-04-13 10:05 ` Toke Høiland-Jørgensen
2014-04-13 14:57 ` Dave Taht [this message]
2014-04-13 17:59 ` Chuck Anderson
2014-04-13 23:24 ` Dave Taht
2014-04-14 9:29 ` Aaron Wood
2014-04-17 21:01 ` Simon Kelley
2014-04-17 21:19 ` Dave Taht
2014-04-20 14:01 ` Chuck Anderson
2014-04-20 15:16 ` Valdis.Kletnieks
2014-04-20 15:41 ` Chuck Anderson
2014-04-13 16:16 ` dpreed
2014-04-13 16:40 ` Dave Taht
2014-04-13 17:57 ` Toke Høiland-Jørgensen
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=CAA93jw5JoQWL5Grq+qH1ypu-QzTLdKKnJkgxoa3iaoKUk-G5gg@mail.gmail.com \
--to=dave.taht@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