2022 domain controllers showing dcdiag errors but replication works

Question

I just built two new 2022 domain controllers and I'm trying to resolve some errors showing in up in DCDIAG tests. Both machines are on the same server in the same virtual environment on the same network with no firewalls between them. Nothing is live yet, the only use they have even gotten is when I added a user in AD to test replication and it does seem to work just fine, the user shows in up Users and Computers on the second DC quickly. Both servers have proper static IPs, gateway, each pointing to the other as primary DNS and themselves as secondary. I've run numerous REPADMIN test and both servers appear to pass all tests. The major errors in DCDIAG are 1723, 1726 and 1753, I just can't seem to resolve them. I do get an event error of 4013 (DNS-Server-Service) once per reboot but DNS starts and is running shortly after that error. I've attached the DCDIAG output from DC1, DC2 pretty much shows the same thing. dcdiag.log

Answer 1

Hello Andy Forbes,

Thank you for posting in Q&A forum.

Are both the two DCs also DNS servers? If so, you can install DNS role on both DCs. And make both DCs point towards each other from the start, with secondary being themselves.

Then run commands ipconfig /flushdns and ipconfig /registerdns on both Domain Controllers.

Here is a similar thread for your reference. https://community.spiceworks.com/topic/2198336-winserver-2016-seeing-replication-errors-in-ad-dc-dont-know-how-to-resolve?page=1#entry-8278239 Here is a link to troubleshoot the event ID 1753.
https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/replication-error-1753-there-are-no-more-endpoints-available-from-the-endpoint-mapper

I hope the information above is helpful. If you have any questions or concerns, please feel free to let us know. Best Regards, Daisy Zhou

If the Answer is helpful, please click "Accept Answer" and upvote it.