Win7 client, IPv6 network, multicast DNS equests and BIND name server?

[Mattia Rossi]

Am 28.03.2013 15:58, schrieb Mattia Rossi:
> Am 28.03.2013 14:49, schrieb Lev Serebryakov:
>> Hello, Freebsd-net.
>>
>>   This question is not very FreeBSD specific, but as my router and DNS
>> server are FreeBSD-based, I think a could ask it here and don't
>> subscribe do BIND-related list, Ok?
>>
>>   When DHCPv4 is not available, Win7 clients on my network pick up
>> proper IPv6 prefix, but cannot pick up DNS server name from router
>> advertisment. In such situation Win7 clients try to use ff01::
>> multicast addresses for DNS resolution.
>>
>>   I have bind server, which listens on all addresses (udp6 *:53), but
>> it seems, that it doesn't answer on these requests :(
>>
>>   Is it possible to configure BIND (system one) to process such
>> requests?
>>
> In my experience you need to run a DHCPv6 server along with the rtadvd 
> daemon to get the DNS server to your Win7 box.
> In rtadvd.conf set the raflags to:
>      :raflags="o":\
>
> This tells the client to look for a DHCPv6 server, and to grab the 
> information supplied there.
> In your dhcpd.conf (ISC DHCPD) then you need an entry like this:

Sorry, should be dhcpd6.conf
>
> subnet6  2001:db8::/64 {
>         option dhcp6.name-servers 2001:db8::1;
> }
>
> Where the subnet has to reflect the actual subnet configured on the 
> interface you're sending out DHCP offers.
>
> In rc.conf add:
>     dhcpd6_enable="YES"
>     dhcpd6_ifaces="em0" or whatever interface DHCP should listen on.
>
> And now your Win7 should be happy.
>
> Win7 using ff01: for DNS lookups seems a bit strange to me, as I 
> thought that Win7 is using LLMNR 
> (http://en.wikipedia.org/wiki/Link-local_Multicast_Name_Resolution), 
> the counterpart to MDNS (http://en.wikipedia.org/wiki/Multicast_DNS) 
> to look up names on the local Lan and to discover services 
> (http://en.wikipedia.org/wiki/Zero_configuration_networking). Both use 
> addresses from the ff02: range.
>
> I've looked into getting MDNS to update BIND like DHCP would do for 
> DDNS, but had no luck to get that going.
> I don't think LLMNR could interoperate with BIND at all.
>
> Hope that helps.
>
> Cheers,
>
> Mat
>