Markus Hartung <m...@hartmark.se> writes: > Hello, > > Anyone here that is more knowledgeable about IPv6 and Windows 10 hosts? > > I have set up my dnsmasq as a authoritative DNS server and have enable ra with > these options: > > enable-ra > dhcp-range=tag:eno1,::1,::FFFF,constructor:eno1,ra-names,24h > > It seems that my linux hosts are correctly getting a IPv6 address and > registers > correctly a AAAA-record in the DNS server. > > My Windows 10 host gets an IPv6 address but doesn't get any AAAA-record. > > Can anyone shed any light on the situation? Do the linux and windows > hosts get their IPv6 differently? And is there a way to get windows to > register an AAAA-record?
My guess is that Windows 10 implements RFC7217: https://tools.ietf.org/html/rfc7217 If this is the case, there is no way for dnsmasq to predict the IPv6 address of a new client (which is what ra-names relies on), and so you can't get the AAAA record. A way to get naming is to use ohybridproxy: https://github.com/sbyx/ohybridproxy - this will query mdns on the network for AAAA records when asked. However, I am not sure if there is a way to integrate this with the authoritative server in dnsmasq (but if there is, I would love to know about it). -Toke _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
