[Dnsmasq-discuss] IPv6 ra-advrouter mode doesn't create the appropriate AAAA records
simon at thekelleys.org.uk
Tue Oct 14 20:46:50 BST 2014
On 14/10/14 19:33, Nilesh Govindrajan wrote:
> On Tue, Oct 14, 2014 at 11:19 PM, Simon Kelley <simon at thekelleys.org.uk> wrote:
>> On 14/10/14 04:09, Nilesh Govindrajan wrote:
>>> Hi list,
>>> I'm playing with IPv6 after getting a tunnel from HE. I have
>>> configured dnsmasq as:
>>> dhcp-range=<my ipv6 subnet>::, ra-advrouter
>>> All machines on my network get IPv6 addresses, but when I try to find
>>> them via DNS request, it fails (doesn't return an AAAA record). But
>>> the corresponding A records exist and they work properly.
>>> This works if I set ra-names mode, but I don't want to use SLAAC.
>> You _are_ using SLAAC, that's what ra-advrouter does.
>> To use DHCPV6, use something like
>> dhcp-range=<my ipv6 subnet>::2, <my ipv6 subnet>::200
>> That way your clients should get DHCPv6 leases, and from them, AAAA records.
> I think with the current setup both SLAAC and DHCPv6 are being used
> because I see two IPs on each machine.
With the configuration you quote above, there will be no DHCPv6. SLAAC
normally results in at least two addresses, one is derived from the MAC
address of the interface, and the second is a random "privacy address".
The later will be regularly replaced.
IPv6 is a whole different world.
You're right that Android can't do DHCPv6. That was the original
motivation for the ra-names mode in dnsmasq.
More information about the Dnsmasq-discuss