On 26/02/13 06:39, Fernando Gont wrote:
Hi, Ted,
On 02/22/2013 04:44 PM, Ted Lemon wrote:
On Feb 22, 2013, at 10:01 AM, Michael Thomas <[email protected]> wrote:
Right now, I don't think that sufficient energy is being given to
just one obvious problem: how does real DNS interact with prefix
delegation in the home (assuming that we don't want split horizon
dns)? For that matter, let me be even more blunt: I don't think
that real DNS is being given enough attention altogether in home
settings, and until that happens we'll just inherit all of the
awful hacks that are done with NATv4.
Agreed. I'm delighted to hear that Simon has a hack in dnamasq that
addresses this problem in a dual-stack environment, but I want to
have a serious conversation somewhere about how to address the
problem on the v6-only homenet.
Who's interested in sketching a DNS-based solution to the problem and
has time to work on it?
I've been lurking for the most time, so.. double-checking: essentially,
what you want is that you always keep DNS for nodes in the internal
network, and those entries remain up-to-date e.g. in the presence of
renumbering? (I guess dynamic updates by each client is not acceptable,
so there should be some kind of "proxy" doing the job for the local net,
right?)
Dnsmasq handles this already in the "guess slaac-addresses" case. When a
new prefix is added to the network, dnsmasq advertises it and goes
through the existing DHCPv4 leases and pings the new putative addresses,
adding any that respond as AAAA records.
I'm not sure that hosts using stateful DHCPv6 fare so well, not least
because I don't really understand what is meant to happen in the DHCP
protocol in such circumstances.
If I got your problem statement right, I'd argue that there are,
essentially, two problems here:
1) Learning the IPv6 addresses in use
2) Updating the DNS accordingly
Dnsmasq does both of these for internal DNS, it's just an extension of
what it has always done in IPv4 land. There's a new test release that
does the same for external DNS, by acting as the authoritative server
for a zone, and/or providing zone transfer to other authoritative servers.
"1" is already solved by <http://www.si6networks.com/tools/ipv6mon>.
"2" could be an add-on to ipv6mon, that would do the DNS updates
according to the address changes.
If the above sounds sensible, I voulteer to:
1) Write the code that does what I've described above
2) Write an I-D that describes what I've done with the code. :-)
Simon.
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
