Pretty generic domain: Two DC's, ServerA and ServerB. Server B crashed one night, and it turned out to be the On/Off switch. Once I replaced that, it came back up, but there is a problem with DNS for some reason.
On ServerB, DCDiag /test:DNS gives:
Starting test: Connectivity
The host 5e864aa9-dbc3-4258-8b27-69e53267ef60._msdcs.domain.local could no
t be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(5e864aa9-dbc3-4258-8b27-69e53267ef60._msdcs.domain.local) couldn't be
resolved, the server name (serverb.sks.local) resolved to the IP address
(192.168.1.98) and was pingable. Check that the IP address is
registered correctly with the DNS server.
......................... SERVERB failed test Connectivity
Testing server: Default-First-Site-Name\ServerB
DNS Tests are running and not hung. Please wait a few minutes...
Running partition tests on : ForestDnsZones
Running partition tests on : DomainDnsZones
Running partition tests on : Schema
Running partition tests on : Configuration
Running partition tests on : Domain
Running enterprise tests on : domain.local
Starting test: DNS
Test results for domain controllers:
DC: ServerB.Domain.local
Domain: Domain.local
TEST: Basic (Basc)
Error: No LDAP connectivity
TEST: Records registration (RReg)
Error: Record registrations cannot be found for all the network a
dapters
Summary of DNS test results:
Auth Basc Forw Del Dyn RReg Ext
________________________________________________________________
Domain: sks.local
ServerB PASS FAIL PASS PASS PASS FAIL n/a
......................... domain.local failed test DNS
In the DNS console on both servers, ServerB has the correct GUID. In ADUC, on ServerB, operations masters show ERROR. If you change them to ServerB, the change takes effect on both servers, but if you change it back on ServerA, it shows ERROR again on ServerB. The DNS test runs clean on ServerA.
It has only been like this for a day, and frankly I might not have noticed anything, except I made a small change to a logon script, and a user complained the change hadn't taken effect. Sure enough, no replication.