Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
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] coping with ipv6 source routing and dns
Date: Wed, 29 Jan 2014 23:30:34 +0100	[thread overview]
Message-ID: <87lhxy2zg5.fsf@alrua-x1.kau.toke.dk> (raw)
In-Reply-To: <CAA93jw5fi=ZAFCEaJofcx2DFpq9cRp7AHc7V=kLiyzw5=8ri6w@mail.gmail.com> (Dave Taht's message of "Wed, 29 Jan 2014 14:10:18 -0800")

[-- Attachment #1: Type: text/plain, Size: 570 bytes --]

Dave Taht <dave.taht@gmail.com> writes:

> Since most forwarders can't be trusted to return NXDOMAIN, an internal
> email box at several of my sites runs dns directly. A few dnsrbl
> providers offer ipv6 transport, so it's possible.

Ah, I see. I just run bind on cerowrt. Have to set an ntp server by IP
(or in /etc/hosts; I use an internal GPS-backed server) to bootstrap,
but otherwise it works well.

> One advantage of dnssec is we get NXDOMAIN working again, so a
> forwarder can be used...

Presumably only if the forwarder doesn't strip the dnssec stuff?

-Toke

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]

  reply	other threads:[~2014-01-29 22:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-29 19:22 Dave Taht
2014-01-29 22:02 ` Toke Høiland-Jørgensen
2014-01-29 22:10   ` Dave Taht
2014-01-29 22:30     ` Toke Høiland-Jørgensen [this message]
2014-01-29 22:36 ` 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=87lhxy2zg5.fsf@alrua-x1.kau.toke.dk \
    --to=toke@toke.dk \
    --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