Is the server configured correctly, dcdiag test?

Question

Domain Name System

Hello everyone.
Please tell me if the server is configured correctly, judging by the dcdiag report?
Starting test: SystemLog
A warning event occurred. EventID: 0x80040022
Time Generated: 10/10/2018 13:54:44
Event String: The driver disabled the write cache on device \ Device \ Harddisk0 \ DR0.
An error event occurred. EventID: 0x00002720
Time Generated: 10/10/2018 13:55:19
Event String:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
A warning event occurred. EventID: 0x000003F6
Time Generated: 10/10/2018 13:55:34
Event String:
Name resolution for the name _ldap._tcp.dc._msdcs.interfreight.local. timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x000003F6
Time Generated: 10/10/2018 13:55:34
Event String:
Name resolution for the name _ldap._tcp.dc._msdcs.interfreight.local. timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x000727AA
Time Generated: 10/10/2018 13:56:02
Event String:
The WinRM service failed to create the following SPNs: WSMAN/SRV-VDC1.interfreight.local; WSMAN/SRV-VDC1.
A warning event occurred. EventID: 0x00000086
Time Generated: 10/10/2018 13:56:06
Event String:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
A warning event occurred. EventID: 0x0000000C
Time Generated: 10/10/2018 13:56:06
Event String:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
An error event occurred. EventID: 0x0000168E
Time Generated: 10/10/2018 13:56:14
Event String:
The dynamic registration of the DNS record '_ldap._tcp.interfreight.local. 600 IN SRV 0 100 389 SRV-VDC1.interfreight.local.' failed on the following DNS server:
A warning event occurred. EventID: 0x00000086
Time Generated: 10/10/2018 13:56:14
Event String:
NtpClient was unable to set a manual peer to use as a time source because of DNS resolution error on 'time.windows.com,0x9'. NtpClient will try again in 15 minutes and double the reattempt interval thereafter. The error was: No such host is known. (0x80072AF9)
A warning event occurred. EventID: 0x000003F6
Time Generated: 10/10/2018 13:56:14
Event String:
Name resolution for the name interfreight.local timed out after none of the configured DNS servers responded.
A warning event occurred. EventID: 0x00000090
Time Generated: 10/10/2018 13:56:22
Event String: The time service has stopped advertising as a good time source.
A warning event occurred. EventID: 0x00001796
Time Generated: 10/10/2018 13:57:44
Event String:
Microsoft Windows Server has detected that NTLM authentication is presently being used between clients and this server. This event occurs once per boot of the server on the first time a client uses NTLM with this server.
A warning event occurred. EventID: 0xC000042B
Time Generated: 10/10/2018 13:58:03
Event String:
The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: The specified domain either does not exist or could not be contacted.
An error event occurred. EventID: 0x00000469
Time Generated: 10/10/2018 14:01:01
Event String:
The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
An error event occurred. EventID: 0x00002720
Time Generated: 10/10/2018 14:03:03
Event String:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
A warning event occurred. EventID: 0x0000000C
Time Generated: 10/10/2018 14:08:10
Event String:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
An error event occurred. EventID: 0x0000272C
Time Generated: 10/10/2018 14:13:34
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using any of the configured protocols; requested by PID 1be0 (C:\Windows\system32\dcdiag.exe).
An error event occurred. EventID: 0x0000272C
Time Generated: 10/10/2018 14:13:51
Event String:
DCOM was unable to communicate with the computer 192.168.0.1 using any of the configured protocols; requested by PID 199c (C:\Windows\system32\dcdiag.exe).
......................... SRV-VDC1 failed test SystemLog
Starting test: VerifyReferences
......................... SRV-VDC1 passed test VerifyReferences

Answer 1

no, read the output of the utility, Google translator will not always help.