Hello,
I am having some trouble with IPv6 name resolution in local subnet, nslookup time outs from all domain members, however all looks good on domain controller (with integrated AD dns) - over there nslookup resolves instantly without time outs.
At same time there is no problem with Internet browsing, but I guess that is because it runs purely over IPv4?
The weird thing is that IPv6 pings are going through perfectly fine, it is just the nslookup not resolving the names from clients, e.g. from Win2012R2 client, Win7x64, Win8.1 client - it times out, even the DNS server name is unknown, but I can ping it just fine over IPv6 no problem.
On server end nslookup resolves fine with zero time out, some (not all) PTR records exist in DNS reversed zone, I noticed only the win8/2012 computers created them on their own, but none of win7/2008r2 did it automatically.
Any help in testing what might be wrong here?
EDIT:
forgot to add that before enabling manual IPv6 (static) config on some member clients and domain controllers, and enabling DNSes to listen to IPv6 interfaces, there was no time out in nslookup from clients (ther eis still no time out when nslookup is performed directly on domain controllers). I'd like to track down what exactly is causing it, related to IPv6, but not necessarily the root case.