On 22/02/13 13:07, David Lamparter wrote: > On Fri, Feb 22, 2013 at 01:00:48PM +0000, Simon Kelley wrote: >> On 22/02/13 12:30, Ted Lemon wrote: >>> On Feb 21, 2013, at 11:31 PM, Lorenzo Colitti <[email protected]> >>> wrote: >> >>> I think the issue that Michael imagines NPTv6 will address is the >>> transition period, when the washing machine has two IP addresses, and >>> the DNS may not have the new address, or may have both addresses, and >>> he's hoping the gateway will somehow bandage this up. However, the >>> gateway's ability to bandage this up is more imagined than real, and >>> we might as well just fix the underlying problem. >> >> The current development release of dnsmasq can act as an authoritative >> DNS server populated with all hosts on a homenet which it knows about >> from DHCP. Delegate your domain to it, and ensure that the TTL >> configured for DNS is smaller than the deprecated lifetime of addresses, >> and this problem should never arise. > > This only works with stateful DHCPv6 though?
It works as well for clients which do DHCPv4 and SLAAC. IPv6-only hosts would have to do stateful DHCPv6, but the DHCPv4 and SLAAC model covers an awful lot of currently-deployed clients. The IPv4 addresses can be RFC1918, the DHCPv4 lease is used to give dnsmasq the MAC address and name of a client. The authoritative DNS module is configurable to expose global IPv6 addresses and hide RFC1918 IPv4 addresses. Simon. _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
