I'm working on replacing some legacy Windows Server 2003 R2 and Windows Server 2008 DCs with some new Windows Server 2016 DCs. Prior to adding or removing the DCs, I'm working to confirm AD health with basic testing. Repadmin /showrepl and repadmin
/replsummary both run fine with no errors. Also, manual replication tests like simply changing AD user settings replicate fine across my single domain setup consisting of multiple AD sites and subnets. However, when I run specific DCdiag
test for DNS, I'm getting inconsistencies in the tests. If I run dcdiag /test:DNS /DNSALL /e /v on a newly installed Windows Server 2016 DC, all tests complete fine for Auth Basc Forw Del Dyn RReg and Ext. But when I run this same test on
a Windows Server 2003 R2 or 2008 DC, I get FAIL on Forw and WARN on Basc and RReg.
My question is why does DCdiag return healthy results when running on Server 2016 DCs but failures and warnings on Windows 2003 and 2008 DCs for DNS? And are Forw and RReg tests critical failures that will likely block the promotion of new DCs?
Here's the results of the tests:
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: wellspring.local houdc01 PASS WARN FAIL PASS PASS WARN PASS
atldc1 PASS WARN PASS PASS PASS WARN PASS
atldc01 PASS WARN PASS PASS PASS WARN PASS
arldc02 PASS WARN PASS PASS PASS WARN PASS
......................... wellspring.local failed test DNS
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: wellspring.local houdc01 PASS PASS PASS PASS PASS PASS PASS
atldc1 PASS PASS PASS PASS PASS PASS PASS
atldc01 PASS PASS PASS PASS PASS PASS PASS
arldc02 PASS PASS PASS PASS PASS PASS PASS
......................... wellspring.local passed test DNS