[Dnsmasq-discuss] Windows ipv6 hostname

Markus Hartung mail at hartmark.se
Mon Dec 19 23:54:10 GMT 2016


On 2016-12-19 06:18, Toke Høiland-Jørgensen wrote:
> Markus Hartung <mail at hartmark.se> writes:
>
> ...
> 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.

It's a shame the windows 10 IPv6 implementation lacks those stuff.
>
> 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).
Thanks for the information, but I have managed to compile ohybridproxy 
and have no idea on how to use it.

> -Toke
- Harre



More information about the Dnsmasq-discuss mailing list