So far, here are some issues I've seen:
The AD Configuration Wizard does not like this configuration. Even with a static IPv6 address and
1: IPv4 disabled, it gives a warning no static IP addresses are configured.
2: If you log on to a workgroup client as Administrator, but the password differs from the Domain Administrator password, you do *not* get "password is incorrect". Instead, you get "System Error 66: The Network resource type is not correct"
3: Attempting to join a client to the domain results in an error:
An Active Directory Domain Controller (AD DC) for the domain "domain.name" could not be contacted. Ensure the domain name is typed correctly. If the name is correct, click Details...
In the details it clearly states (no addresses found).
DCDIAG on the server fails the Connectivity test (GUID._msdcs.Domain.name record not found). In DNS Manager, it is present as a CNAME record, but fails to resolve from a ping. The same is true using the FQDN, but not NetBIOS name.
Ultimately, this is because the HOST (A/AAAA) record does not register in DNS.
The goal here is to have an environment free of IPv4 entirely.
So is IPv4 Required for ADDS? If so, the wizard should inform not only is a static IP needed, but that IPv4 is required and a static IPv4 address is also required, not just "no addresses found".
Or am I missing something to get this all working with an IPv6-only environment?
I will keep banging on it myself, but if someone knows, it would be appreciated.
There is an amazing pack of free network admin tools. click here to download it
Other recent topics
