Despite having a valid IPv6 address and being able to communicate with other IPv6 hosts, a Windows 10 system on my LAN is igonring AAAA responses and as such will not initiate IPv6 traffic.
nslookupwill show the A record for a domain, but not the AAAA record, even though I can see in Wireshark that the AAAA query is sent and a valid response is received.
nslookupworks as expected and if I query an IPv6 address I get back the expected hostname.
ping -6works when I go directly to another IPv6 address, but not when I enter a hostname. This is likely an artifact of the ignored AAAA response mentioned above.
- IPv4 works as expected.
- Dual-stack Linux and BSD systems on the same subnet with the same nameserver work as expected.
I found this (https://support.microsoft.com/en-us/help/929852/guidance-for-configuring-ipv6-in-windows-for-advanced-users) about preferring IPv4 over IPv6, but I do not have those registry keys set.
Edit: Does it matter that my nameservers only listen on IPv4?