On 02/26/2013 10:15 AM, Simon Kelley wrote:
On 26/02/13 15:07, Michael Thomas wrote:
On 02/25/2013 11:52 PM, Simon Kelley wrote:
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.
I'm not understanding: what is the name that it associates with the
address?
A synthesized one like ISP's often do with forward map addresses in their
dynamic pool?
Either the name that the host provides in a DHCP hostname or FQDN option, or a
name associated with the host in the dnsmasq configuration. Most DHCP clients
provide the hostname in their DHCP requests these days. Dnsmasq configuration
allows associating a name with a MAC address or client-id.
Ah, ok. But that wouldn't work in a SLAAC environment unless it did a DHCP
INFORM, right? Hosts don't do that generally, right?
Mike
_______________________________________________
homenet mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/homenet
