Earlier I was having issues connecting one of my workstations (client) to my domain, and I thought it was because the domain was not in my possession yet (reference: this question). But, due to the answer I'm led to believe that there is something else going on? I've searched the internet and can't really find out why I'm still having issues, so I figured I'd ask to see what the possible causes of this error message could be. Here is my setup:
Server (DC) ============================== IP: 192.168.0.2 Subnet Mask: 255.255.255.0 Default Gateway: 192.168.0.1 Preferred DNS: 192.168.0.2 Workstation ============================== IP: DHCP Subnet Mask: Default Gateway: Preferred DNS: 192.168.0.2
Additionally, I have a Forward Lookup Zone for my local domain (internal.domain.com). Here is a dump of both the client and server's nslookups:
> nslookup internal.domain.com Server: cdns02.comcast.net Address: 2001:558:feed::2 Non-authoritative answer: Name: internal.domain.com Address: 50.19.***.*** (definitely not my IP address) > nslookup -type=SRV _Kerberos._tcp.dc._msds.internal.domain.com Server: cdns02.comcast.net Address: 2001:558:feed::2 primary name server = ns.buydomains.com responsible mail addr = hostmaster.buydomains.com serial = ... refresh = ... retry = ... expire = ... default TTL = ...
This shows up equal on both the server and the client, which makes me think that both of them are not using my server as the DNS lookup, which is why I'm having issues? I'm really not sure what's going on here. Just looking for what could possibly be an issue, and I tried to answer most of the followup questions on the answer to my previous question.
I used this question's answers to generate a pseudo-unique IPv6 address, which was in the format of xxxx:xxxx:xxxx:xxxx::/64. Here are the settings I used on my server:
Server (DC) IPv6 ============================================================= IPv6 Address: xxxx:xxxx:xxxx:xxxx::1 Subnet Prefix Length: 64 Default Gateway: xxxx:xxxx:xxxx:xxxx:ffff:ffff:ffff:ffff
I went into my router and changed the IPv6 settings as well. It had stated "
Obtain a DNS server address automatically or enter a specific DNS server address.", in which case I selected to specify the DNS Server Address to the static address of my server. I also setup Google's public DNS server as the secondary.
Finally, my client machine was able to join the network instantly. Also, just for good measure I set the client machines IPv6 DNS to point to my server (again, just for good measure).
If anyone else runs into an IPv6 issue, this seems to be the solution. What's nice is that I can use the RSAT now to manage my server from my primary client (I can remove my monitor, keyboard, and mouse from the server).