Here is the dcdiag results. Doesn't look too good!
-------
Domain Controller Diagnosis
Performing initial setup:
* Verifying that the local machine server, is a DC.
* Connecting to directory service on server server.
* Collecting site info.
* Identifying all servers.
* Found 1 DC(s). Testing 1 of them.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site\SERVER
Starting test: Connectivity
* Active Directory LDAP Services Check
6a428c2b-790a-4a5a-8609-e5f71af7adc8._msdcs.schoolname.local's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(6a428c2b-790a-4a5a-8609-e5f71af7adc8._msdcs.schoolname.local)
couldn't be resolved, the server name (server.schoolname.local)
resolved to the IP address (192.168.1.2) and was pingable. Check that
the IP address is registered correctly with the DNS server.
......................... SERVER failed test Connectivity
Doing primary tests
Testing server: Default-First-Site\SERVER
Skipping all tests, because server SERVER is
not responding to directory service requests
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels
Running enterprise tests on : schoolname.local
Starting test: Intersite
Skipping site Default-First-Site, this site is outside the scope
provided by the command line arguments provided.
......................... schoolname.local passed test Intersite
Starting test: FsmoCheck
GC Name: \\server.schoolname.local
Locator Flags: 0xe00001fd
PDC Name: \\server.schoolname.local
Locator Flags: 0xe00001fd
Time Server Name: \\server.schoolname.local
Locator Flags: 0xe00001fd
Preferred Time Server Name: \\server.schoolname.local
Locator Flags: 0xe00001fd
KDC Name: \\server.schoolname.local
Locator Flags: 0xe00001fd
......................... schoolname.local passed test FsmoCheck