Brand new Server 2022 Installation- DNS will not function, waiting on AD DS Sync

Question

I am learning servers as a new student. I have a server that had a blank HD. I installed Windows Server 2022 Desktop Experience- Evaluation. I have promoted the server and set up DNS/AD. The next step is to add a workstation to the domain. The desktop can see the server using ping, NMAP, Advanced IP Scanner, but when I set up the configuration to connect to the domain, the computer is unable to connect or even see the domain. It reports it is unable to find the domain. In Server Manager under DNS and AD DS I see:

"HOMESERVER01 4013 Warning Microsoft-Windows-DNS-Server-Service DNS Server 4/29/2023 10:02:38 PM"

and the associated text:

"The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed."

I have tried searching the internet, I have checked the Registry for all the suggested flaws, none there. I have completely dumped the system and reinstalled it, with the same results. Attached is the Network Configuration. The server and workstation are both on a small router 192.x.x.x which is connected to a network 10.x.x.x. in an attempt to isolate them to determine what is happening.

I know I am writing a long essay, but I am getting frustrated, any help would be appreciated.

Answer 1

Please run;

Dcdiag /v /c /d /e /s:%computername% >C:\dcdiag.log (run on PDC emulator)
repadmin /showrepl >C:\repl.txt (run on any domain controller)
ipconfig /all > C:\%computername%.txt (run on EVERY domain controller)
ipconfig /all > C:\problemworkstation.txt (run on problem pc)

Also check the domain controller System and Replication (DFS or FRS) event logs for errors since last boot. Post the Event Source and Event IDs of any found. (no evtx files)

then put unzipped text files up on OneDrive and share a link.

Answer 2

Now looks like there is a rouge IPv6 DHCP server on the network (possibly a router?) You'll need to either properly configure the static IPv6 addresses on your network or much simpler would be to disable the IPv6 DHCP server. I can't comment on the problemworkstation because script was also run on the server.

Answer 3

Ok, sorry for the delay in response.

First, I want to thank you for taking the time to help me.

So, I installed a fresh drive and server installation. Then I created the domain again, with the same result. I looked at the codes and found one mentioning WINS. I went into the DNS settings and there was no entry in DNS for WINS, so I created one and everything worked.

I restarted the orginal installation we have been troubleshooting and created the WINS entry, everything now works.

Once again, thank you for the help and patience.