search for: hpnb

...the PTR entries and it's not meant to be used in production. The intention was to verify whether those failed DNS updates might have an impact on the GPO update issue. It turned out they don't. I am now able to forward-and-reverse lookup the client address: C:\Temp>nslookup CYB64W10-HPNB.ad.cyberdyne.local Server: skynet.ad.cyberdyne.local Address: fdea:5b48:d4c1:1:1::6 Name: CYB64W10-HPNB.ad.cyberdyne.local Addresses: fdea:5b48:d4c1:1:1::102 fdea:5b48:d4c1:1:ec71:fc72:a95b:3d12 10.0.1.186 C:\Temp>nslookup fdea:5b48:d4c1:1:1::102 Server: skynet.ad...

Perhaps I am on the wrong track but I would like to share some additional observations... I quickly enabled DNS query logging: # rndc querylog Then run another gpupdate on the client. During the Update I see lots of queries: 04-Aug-2016 14:46:58.414 queries: info: client 10.0.1.186#59270 (_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ad.cyberdyne.local): view internal: query:

...ts correct but if windows is buggy.. Source : https://support.microsoft.com/nl-nl/kb/2891966 It was worth a try.. https://support.microsoft.com/en-us/kb/2954031 for the status rapport error, one you can check also. I see still something incorrect here. > C:\Temp>nslookup cyb64w10-hpnb > Server: skynet.cyberdyne.local > Address: 10.0.1.6 > C:\Temp>nslookup cyb64w10-hpnb > Server: skynet.cyberdyne.local > Address: 10.0.1.6 > > Name: cyb64w10-hpnb.ad.cyberdyne.local > Address: 10.0.1.186 SKYNET.AD.CYBERDYNE.LOCAL is the correct AD DC location....

Forgot one extra. On the win 10, check this reg key. HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Hostname It states you hostname here, but if its not in caps change it to HOSTNAME In that register key. (HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters) You should see also you dnsdomain at Domain and NV Domain. NV Hostname should be in CAPS also. The domains not.

Just I missed the correct IPv6 PTR record from the DNS.                                     Ok and whats obligated for a correct working kerberos environment. Ahh.. Yes... dns A and PTR records. ;-) so one thing fixed thats ok..     The PC, ( ipconfig /all ) looks good now.     Next.. your hosts files... > my /etc/hosts: > > # IPv4 and IPv6 localhost aliases >