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:36:06 +0100 [thread overview]
Message-ID: <87ha8m2z6x.fsf@alrua-x1.kau.toke.dk> (raw)
In-Reply-To: <CAA93jw5WAanz+hygGFHRNGsD=k1J3rC1ge_EVJgEGsC8oHGjHw@mail.gmail.com> (Dave Taht's message of "Wed, 29 Jan 2014 11:22:16 -0800")
[-- Attachment #1: Type: text/plain, Size: 893 bytes --]
Dave Taht <dave.taht@gmail.com> writes:
> But this doesn't help in terms of reverse lookups (I think),
> where I might or might not have my own delegated subdomain.
>
> from
>
> someoption=
> comcast.assigned.ipv6.address.range/60 lookup via 2001:558:feed::1 or ::2
> someoption=
> he.assigned.ipv6.address.range/48 lookup via 2001:470:20::2
As in, reverse lookup comcast.assign.ipv6.address.range from server
2001:558...etc? Isn't that just another server= option for some part of
ip6.arpa?
> and then there's splitting dns... where I might want nuc.hm.armory.com
> AAAAs available to the outside universe. somehow.
Assign a parent domain to a public server and subdelegate as appropriate
From there? (I think?)
> My brain hurts.
Well the 'distributed' part of DNS is not really meant to be distributed
in the true non-hierarchal sense, I suppose. :P
-Toke
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 489 bytes --]
prev parent reply other threads:[~2014-01-29 22:34 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
2014-01-29 22:36 ` Toke Høiland-Jørgensen [this message]
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=87ha8m2z6x.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